Design pattern for file based communication? -
I have to expand an existing program (Java is based, but it should not be counted). This program should communicate with any other program X.
This program is X. The UI is a little small and only supports file based communication. This means that I have to put my file in a certain folder. "Answer" is placed in another folder, where I have to choose it.
Are there any design patterns for such communication? If I think about it, the problem of file locking, unfolded io-streams etc. comes to my mind.
Do you have some more descriptive keywords for my googleing? "File based communication" does not take it.
Perhaps the pattern you want
I want to improve the article in Wikipedia Find articles. But the description of the main concepts is quite clear there (just replace 'buffer' with 'file' for your concrete case).
Comments
Post a Comment