Thanks Remy,
The only problem is that the server is not mine. It is served from a DCB
etherpath rs-232/tcpip converter. I suppose I could use a proxy but I am
not ready to go down that path. I took the sample IPC code and used it.
WHen the main app detects an On connect event, it releases the port. When
my little applet closes, the main app re-acquires the connection. Seems
pretty stable and if it fails, I have a back-up process.
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:457ba75d$1@newsgroups.borland.com...
>
> "Larry" <lkillen@charter.net> wrote in message
> news:457aca69@newsgroups.borland.com...
>
>> Can I send a message from the worker app to the main app and direct it
>> to close the connection and at the end of my setup, direct it to
> reconnect?
>
> You can, but it would be easier to just design the server to allow both
> client connections to run simultaneously, and then serialize access to the
> rs-232 port as needed. Since the clients are not connected directly to
> the
> rs-232 port to begin with, the server has to delegate the client
> operations
> anyway. So it can control which client accesses the port at any given
> moment. That way, the two apps don't need to communicate with each other
> at
> all.
>
>
> Gambit
