Hi, You can store information in session in both sides. So if you have to store status (for example), you can store in both sides the same info (or different, depending on your business protocol) and as each session is associated to a unique couple (server/client), the info stored inside will only be related to this couple. So you can follow status between client and server using session information with your own business logic. You could also give a try to the statemachine, even if I didn't try it until now, it could answear your needs.
Frederic ----- Original Message ----- From: "tdi" <fred.bregier wrote: What is my problem is acctually howto handle that response in code. Should i do it in session (stored some state) or how? What is want is to have API with wrappers like method: getData() which sends something and returns a response from the other side. I do not acctually know what way it should be done properly. My guess was to have some state stored in session and this way handle responses etc. (like state='sent', so next messageReceived would be answer for the dat sent before.
