I'm fairly new to Mirth. I'm coding an app that will 'listen' for Mirth to deliver a file. When the app detects that a new file is available from Mirth I'm going to process the contents of that file into a DB.
Currently the design assumes that the name of the file delivered by Mirth will be fixed.
For example, mirthdata.xml.
My question is this.
In the event, presumably common, that Mirth delivers a new file while my app is processing the previous file what options does Mirth have for waiting until that processing finishes to avoid conflicts?
For background, my 'listening' code is based on Apache Commons VFS. I create a thread that uses this API to detect timestamp changes on a file, and when a change is detected, it calls the DB access code.
Any ideas appreciated, even better ones. :>)
Currently the design assumes that the name of the file delivered by Mirth will be fixed.
For example, mirthdata.xml.
My question is this.
In the event, presumably common, that Mirth delivers a new file while my app is processing the previous file what options does Mirth have for waiting until that processing finishes to avoid conflicts?
For background, my 'listening' code is based on Apache Commons VFS. I create a thread that uses this API to detect timestamp changes on a file, and when a change is detected, it calls the DB access code.
Any ideas appreciated, even better ones. :>)
Comment