Piping Files

File contents can be piped to another application by omitting the local destination and providing a pipe "|" or redirect ">" command.  It is not necessary to use the "-D" display option when output is being piped or redirected.  For example, to page through a remote text file:

movedat example.com:readme.txt | less

This is particularly useful when combined with Object Handlers that call on archiving utilities.  For example, if you had a handler named tgz that produced gzip tar streams, your syntax might be:

movedat example.com=tgz:MyDirectory | tar -zxf -

You can also pipe data into movedat (via stdin) by specifying a dash "–" as the source.  For example, to send the output of myapp to the server "example.com", you could type:

myapp | movedat - example.com:output

On Windows, the performance of piping may not be as good as on other platforms or as targeting a file directly.

For gigabit or faster networks, or when piping to programs which may block, you may wish to increase the StreamSize.

Retry & Failover

Prior to beginning a piped transaction, movedat will ping the server or host group and begin Automatic Retry if no server is available.  Once a piped transaction has begun transferring data, retry is no longer possible and a failure will terminate the session.