Of course brilliant! I currently have a very simple web architecture consisting of a clustered server using inproc sessions. I have no DB so writing and querying the session seems to be the way to go.
If I understand correctly the bus notifies a consumer (which is part of the monorail app) that a reply has arrived. The consumer then writes this message to the session to be later queried by the AJAX. Correct? With inproc sessions I'm not sure my consumer would have access to write to another sessions data. I suppose I could create a simple global list stored in the container and use that to store and retrieve the replies by session id. Would that be a bad idea and the real answer is to use DHT? My web app is not disturbed so I'm guessing using DHT may be like using a sledge hammer to crack a nut. BTW I'm trying to setup a proof of concept for this which I'd be happy to share with the group if it would be of any use. Assuming I can get it all to work of course! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
