See, I was gonna go with Data.txt in a shared network drive.

Btw = if you're worried about conflicts - it's Ok there's a second file called "writeStatus.txt" which you have to claim by replacing the String NULL with your processId - thereby claiming write access to data.txt and causing any other processes to Thread.Sleep until it's free.

Unrelated, who's hiring...

But who has access to writeStatus.txt? Classic rookie mistake. You needed a writeStatusWriteStatus.txt.

Sounds like playing Byzantine Generals on the file system :)

Flat files FTW, Just need to re-invent server-client architecture using freely available tools and you're at management level kudos,

>> I never found out the BEST way to share data between programs. In fact, I'm still looking. I think we all are.

>Copy-paste.

You may joke, but it's the most universally supported, and therefore the most likely to be available.

For Linux users its gotta be the pipe. Works great.

You guys... Forgot about email...