Depending on your web architecture....You send the message to the bus with the session id, and when you get the reply back, you store it back in the session. The ajax call query the session for that information.
Other options would be to put it in the cache, or store in DB and look it up On Wed, Jan 28, 2009 at 5:11 AM, Justin Ramel <[email protected]>wrote: > > Thanks for the reply it's good to know I was heading down a dead end! > > Could you elaborate a bit on your answer? > > For example a customer requests their shipping address from the > website my controller sends a message to the bus and immediately > redirects to a static processing page freeing resource on the web > server. > > The processing page contains some AJAX which I guess would poll the > server every few seconds to see if the customer shipping address had > arrived yet. > > When the backend sends the customers shipping address message to the > bus where does it end up? > > The AJAX client does not have a constant connection (nor do I want it > to have) so how can the bus pass the message on to be consumed? Or can > the AJAX somehow query the bus to see if a response has arrived? > > Does that make any sense or am I heading down another dead end? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
