I read a post by Udi (http://www.udidahan.com/2008/07/30/scaling-long- running-web-services/) and wondered, has anyone has implemented something like this using RSB?
It seems like you'd have a message module on the client side that makes a call using HttpWebRequest to a target url and write the resulting response to disk. Then the client polling mechanism calls a known uri keyed by correlation Id and does the redirect. I already have a way of compiling uri's based on the response message data; for example, if the target url is some kind of 'view' that requires the id contained in the response message. Right now, I am doing things the first way Udi mentions in his post for client redirects, but I'd like to explore the better option he proposes. To keep the resource url's hidden it seems like some kind of url rewriter would need to be employed as well, so the client sees http://my.domain.com/projects/view/id/3 instead of http://my.domain.com/resources?x=somecorrelationid . Am I on the right track with the message module thing? Are there problems with this approach anyone can see? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
