ExpeDat servers can be configured to access arbitrary storage and automation systems, in addition to regular files. Server Object Handlers route ExpeDat Desktop requests to external scripts and applications, creating a gateway to virtual filesystems, programs, and external databases.
Object Handlers must be configured on the server and enabled in the client.
To access server-side object handlers, obtain a list of available handler codes from the server administrator and enter the list into the "Server Handlers" field of the Setup pane in the Options window. The list will consist of one or more short text strings, separated by commas. For example, "DB1,BackEnd,Notify".
Alternatively, administrators can pre-configure a list into an ExpeDat Desktop executable using DropDat embedding.
When a list of handlers is available, a new "Handlers" menu will appear in the center of the main window, allowing the user to choose a handler or "None" to access the regular filesystem.
Using Object Handlers
When a handler is selected from the Handlers menu, all transactions will be routed to the corresponding application on the server. A handler may support any of the basic ExpeDat Desktop file transfer and maintenance functions. Contact the server administrator to find out the exact capabilities and limitations of each handler.
The "Remote Path" field will be renamed "Remote Prefix". The handler may interpret the text in any way it sees fit: it might not be a file path. This can be useful for providing additional information to the handler.
When a handler is selected, the following limitations apply:
- Inline compression is not available. The Compression checkbox will be disabled.
- Streaming Folders is not available. The Streaming Folders setting will be ignored.
- If a file transfer is interrupted, it cannot be resumed. Automatic Retry will start over from the beginning.
- Progress and speed information may be inaccurate.
- Performance will be limited by the ability of the handler to process data.
- After a file is uploaded, a Send transaction will wait until the handler signals that it has finished processing the data. This may result in a long delay after the progress bar is full.
- The object handler is responsible for reporting errors in processing. Contact the server administrator if you do not understand an error.
Not all handlers will implement all functions. If you receive an "Unsupported Feature" error, the handler you have selected may not be available or may not support the action you were attempting.