Generally with queuing all messages are asynchronous ... basically you setup 2 queues and input queue and an output queue. Your app writes a message to the queue for the other process to pick up and execute. When it is complete it writes a message back to another queue letting you know the result, you generally tie the messages together via a message id. This process is by its nature asynchronous.
For implementation I generally have the page simply write the message then return. If you want to offer a status etc you should have the page refresh to check its status occasionally. The page should *not* wait until a return value is available to return to the user. A perfect example of this would be to do a "processing" page that refreshed (or used ajax) until it was done or to have a page which shows all of your outstanding jobs (I did a status page such as this for a reporting system where requests often took 5-15 minutes) Cheers, Greg On 6/26/06, Paul Cowan <[EMAIL PROTECTED]> wrote:
Hi all, I have the following headache concerning a web app. for which we are entering the design stage of the process. We are doing the front end work and a Microsoft product called Navision is taking care of most the business logic. Another company has been charged with this work. Methods for say creating credit cards for example are handled by Navision. The way the company have handled this is to communicate via MSMQ where by we place xml messages on a queue that are then handled by Navision. This would be fine if we were just placing messages on the queue but sometimes we get xml returned to us that we need to display or process. From an ASP.NET perspective I think I need to look at doing this type of thing Asynchronously. I know in .NET 2.0 you can use asynchronous pages but am wondering how best to model this MSMQ interaction. I don't want to wait for a synchoronous msmq call but don't know if it can be done async. Also will I need to create a windows service to process these queue messages? What are people's thoughts in how I should model this web page interaction with MSMQ, I am thinking of a proxy pattern but maybe there is a better way. Let me know your design considerations. [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
-- If knowledge can create problems, it is not through ignorance that we can solve them. Isaac Asimov =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
