Processing Filespooler Queues Without Filespooler

All of the Filespooler examples so far have focused on using fspl queue-process to process queue items.

However, you can manually process things also by having Filespooler decode the packet for you. OK, so this isn’t technically “without Filespooler” but could be “without Filespooler queues”.

This can take one of several approaches:

  1. You could use fspl queue-info and fspl queue-payload to get the metadata and the payload of the queue, respectively, and process it yourself.
  2. You could use fspl stdin-info, fspl stdin-payload, or fspl stdin-process to deal with Filespooler-format data that may or may not have ever been written to a Filespooler queue. Note that these methods do not provide for sequenced processing.

You might use these if you have a different layer providing queueing, or have more specialized needs. Consult the Filespooler Reference for more details on these commands.

Sometimes, one wants to verify the integrity and authenticity of a Filespooler job file before processing it.

Filespooler lets you request the remote execution of programs, including stdin and environment. It can use tools such as S3, Dropbox, Syncthing, NNCP, ssh, UUCP, USB drives, CDs, etc. as transport; basically, a filesystem is the network for Filespooler. Filespooler is particularly suited to distributed and Asynchronous Communication.