The ECP (Event Controlled Publishing) Server is a standard feature of the Mito.net software. The ECP Server allows the user to enter and queue both the jobs in the MITO.net server and the jobs entered from the network to be processed automatically. Free text like API to easily integrate MITO.net in your application program.
Please see this API script example . The ECP server continuously monitors an unlimited number of folders. Each folder can be assigned to a different user. It's up to the administrator to create those ECP Folders. The administrator creates an ECP Root from which all the ECP Folders are drawn. The administrator will manage access to the folders. Only the authorized users will have access to the system. Periodically the ECP server checks every single ECP folder to check if there are script-files that need to be processed. If the ECP server detects one new script-file it sends it to the Mito.net job queue. Any client on the network can create a script-file through the ECP client software. Alternatively a script-file can be generated from an application program. The script-file is a normal text file. It is similar to a standard .ini file and it has an .ecp extension. The ECP Server front panel provides the user with the status of each scheduled job and the program as a whole.
The ECP Client is a standard feature of Alea's Mito.Net software. It allows - together with the ECP Server - to add a job to the Mito.Net queue from any computer in the network (LAN). Client PC and Server PC "talk" to each other through the exchange of script files. The ECP Client creates the script files and sends them to the ECP Server through the network. The system transfers the files into default folders on the Server (ECP folders). Each ECP client has its own folder or share a folder with another client.
