We developed our own..
Any operator work stations kisStar or webStar just submits jobs to our /efStar server shared folder.
The administrator will have additional functions.
Our efStar application is just another option or tool required for building complete TAS systems.
Any delevopers interested in porting jobs to your own efStar, it quite simple for your projects.. email us. |
"Shared of text files"
..is the concept we have choosen.
One of the crudest, yet simplest methods is to have the client app build a little ASCII text file that contains all the necessary information that the server app needs to schedule a fax on behalf of the client. This file would be placed in a shared network directory that both the client and server apps both have access to.
For example, line 1 of the text file could contain the fax number to send to and line 2 could hold the name of the sender and line 3 would have the actual fax file name. Of course, the faxable file would need to be put in this shared directory so the server app has access to it. The server simply needs to periodically (based on some timer or other event) poll this shared directory and check for the existence of a file it hasn't processed. In this scenario, however, there is not much of a mechanism for the client to get any feedback on the status of the fax. Admin person would monitor external server jobs not sent. |
