If a client talks to server1 and has to wait X number of seconds for a response, the client won't care what server1 has to do to make the response.
Client -> Server1 "Do some work" Server1 -> Server2 "Give me a data set" Server2 -> Server1 "Here" Server1 -> Client "Here is the data you asked me to process" If you call need to go across servers you'll need socket connections. You'll need to open plain socket connections, and then make your own protocol for how messages are sent and received. /B ----- Original Message ----- From: "Tom Sanders" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, January 23, 2003 17:04 Subject: Synchronous (function call type) interface ? > I have two application servers running at different > machines and I want to provide a function call type > (synchronous) interface to applications. > > This operation may mean one server to send/receive > data from another server. Since I want application to > be unaware of such inter-machine communication and > yet provide a synchronous interface, I want client > call to be blocked in local server unless all data is > ready. > > Any suggessions about good ways of achieving this > functionality? Message Q, Pipes, anything? Your inputs > will be appreciated. > > Thanks, > Tom > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
