another option is to have a one way bus from the web to the service. the service will process the message and persist the result to disk (database, pht, etc) the web can then access the persistent storage. this way the web doesn't receive incoming messages. it only sends them out.
On Thursday, July 26, 2012 12:54:36 PM UTC-4, Jason Meckley wrote: > > RSB polls the queue, listening for incoming messages. I don't recall the > exact implementation, but memory and open queues are not an issue. The > thing to remember is that messages are not handled within the context of an > http request, so you will need a mechanism (data cache) to move the result > of handling the message to an http context. the client will poll the > webserver when the request comes in check the data cache for a result and > process accordingly. > > On Thursday, July 26, 2012 8:46:46 AM UTC-4, Daventry wrote: >> >> Hi, >> >> We'd like to use RSB to send/receive messages between a web server and an >> application server that will run a long-running task. >> >> When the long-running task finishes and sends a message back to the web >> server - how's it picked by RSB? Is there a long-running thread watching >> the message queue? We're concerned about having long-running tasks on the >> web server - i.e a thread polling a message queue in this case. If so, are >> there any other alternatives? >> >> BTW - what are the best practices to notify the client about the >> completion of the task? It is a Silverlight client. >> >> Thanks and regards. >> > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To view this discussion on the web visit https://groups.google.com/d/msg/rhino-tools-dev/-/jRqy_l0FvTUJ. To post to this group, send email to rhino-tools-dev@googlegroups.com. To unsubscribe from this group, send email to rhino-tools-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
