Implementing an IMAP IDLE command in a Filemaker solution

The project is to implement an IMAP4 IDLE command as described in RFC 2117 in a Filemaker solution. The project is limited to building a client-side script to : 1 - send the IDLE request to the server (start idling process) 2 - get the results sent by the server (something like open a dialog when results are received) 3 - send the DONE command to the server (terminate idling process) The project is limited to building a script for these 3 steps. It does not include handling the results sent by the server : we already have the scripts that we want to use in that situation. You are just kindly required to assist us implementing a script to start and terminate an IDLE process, and detect the results sent by the server during that process. It is encouraged that the script uses the Monkey Bread Software plugin for Filemaker that enables CURL as well as Socket functions. Info on the plugin (and a demo for you to work with) is available at: [login to view URL] Other workarounds are possible, but the use of any other plugins should be avoided. Specific requirements for the 3 steps : Step 1 : the IDLE command should be run in a non-blocking process : The IMAP IDLE command will typically remain active until Step 3 (termination by client). In Filemaker, the whole IDLE process should run in background in order not to block the Filemaker solution. Step 2 : getting the results sent by the server should ideally be performed by listening for the server response. We prefer that the script listens for server response in order to trigger an action as soon as result is received. Step 3 : sending the DONE command. The script should terminate the IDLING process in a clean way by sending the DONE command, according to the RFC specifications. We do not want to terminate the process by simply killing the connection on the client side. We attach a Filemaker example file, which contains 3 sample scripts, as previously described. Comments on the difficulties that we have are included in the scripts. Please feel free to use this way, or use a different strategy. Please note that we are attached to the simplicity of your solution. We will have a preference for a solution avoiding the use of any additional plugins or adds-on (except, as previously said, the MonkeyBread Software plugin that we already use). Best regards.