Has anyone thought about a scenario in which the server is supposed to do a lot of work to complete a request? In this case a simple request/reply pattern would not work because you would keep the port occupied without having it to be. Is there any suggested communication pattern for such a case? - OctavReceived on Sunday, 24 December 2000 20:26:27 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:41:42 GMT