|
suppose i have a server and N clients.
1) clients need to asynchronously execute remote methods (like JMS remoting, but it doesn't work in Spring 2.0.2 implementation). we currently do it with RMI + threading through AOP on the server side.
2) some chosen methods must be executed sequentially (still in a thread(s) different from the calling RMI thread) - that means that the execution order is vital. however different clients shouldn't be blocked in this case (sortof queue-per-client). a client has it's id, but the methods are not obliged to have it among the parameters.
3) (more user-friendly stuff) the code should be still RMI-style, so that the client doesn't really know what mess it calls =).
can someone point me to a pattern, or to a known solution, or to anything that may help me?
| 
crushed