Multi-standalone communication

[Dar Scott]

On Dec 7, 2006, at 12:21 PM, Richard Miller wrote:

> Dar... I understand the plan here. My concern with this is the  
> constant disk access that would need to take place. The information  
> that needs to be exchanged between these two apps is directly  
> connected to the users experience. So when the user presses a  
> button on App A, they expect to see a rather immediate response.  
> That response will be occurring in App B, but I need it to look  
> like it's all one application. So App B needs to be polling every  
> second or so, as does App A. Is this too much disk access or  
> acceptable?

Richards suggestion of the checking existence of files or mine of  
checking file name changes might minimize that.  You can use that for  
the data, or just as a way to allow polling to know there is data in  
the file.

Depending on what you have in mind, I wouldn't worry too much about  
beating on the disk.  If the computer has to weigh trucks of hogs day  
in and day out over years, then maybe.

> I've played around a little with read/write - to/from processes,  
> but can't get the hang of it yet. Having had no experience with  
> those functions, it may take a bit of work to get that to go. Same  
> goes for sockets... no experience with that either.
>
> And, of course... I'm really hoping to not spend a lot of hours on  
> this issue.

Yeah, that's why I mentioned earlier that fiddling with installing an  
adaptor to a virtual LAN might take more time than you were expecting.

On the other hand, you might decide that getting into sockets is an  
investment that you want to make and reap the benefits beyond just  
this project.

Dar