Well, you could always create an HTTP-based RPC mechanism, based around CSP, WebLink or even PHP. These gateway technologies provide a means of providing "on demand" execution of a procedure/function of your choice on the target "server" process, triggered via an HTTP request from the "client" process. Of course this is the underlying architecture for formal RPC standards such as XML-RPC and SOAP, but it's relatively straightforward to invent your own request and response messages and do your own thing without the overhead of XML parsing. Provided requests and responses are given proper headers, HTTP doesnt really care whats in the message payload.
No reason why you couldn't use this for inter-process communication and it has to be more efficient than polling globals. On Mon, 19 Apr 2004 07:41:38 +0200, "Kristian Kalweit" <[EMAIL PROTECTED]> wrote: >Hi, > >is it possibly to have inter-process communication without polling globals? > >Scenario: > >I have got a multi-threaded TCP Server in an Active-X Control. The server is >started up as job at system start (%ZSTART). Now I want to use this server >from other running processes within Cach�, to send something to connected >clients. > >Regards, > >Kristian Kalweit. > --- Rob Tweed M/Gateway Developments Ltd Global DOMination with eXtc : http://www.mgateway.com ---
