HELP!

[Cable]

Greetings,

I want to build a webservice where I can call it from my web application
when a user triggers the event on demand.

This event will go out and gather some data and store it in a local database.

My big thing is I want one queue where these events can stack up, as the
users of my web app can trigger this event at will, and it is a helper
function (users don’t realize they are kicking off this event), I do not want
500 of these events executing simultaneously during a busy time of my web
app, rather I want to be able stack these things up in one centrally located
queue that execute in the order they were requested.

Basically need some sort of sentinel process that checks this queue every 5
minutes or whatever, and if items are in this queue, they need to be
processed accordingly.

I have never designed anything of this sort, and was just curious what type
of design suggestions those out there...
Your ideas are welcomed and much appreciated....

-Cable

[Jani Järvinen [MVP]]

Cable,

I want to build a webservice where I can call it from my web application
when a user triggers the event on demand.

Given your situation, an asynchronous queue is definitely what you need,
however you could also find othe solutions like worker threads interesting.

Luckily .NET supports Microsoft's Message Queue (MSMQ), and it is really a
breeze to use. The problem with MSMQ is that you are tied to Microsoft's
product, but as you are using .NET anyway, this probably isn't an issue.
Take a look at the classes in the System.Messaging namespace. To send a
message, you can use the MessageQueue.Send method, and to read messages, you
could use MessageQueue.Receive method (among others).

You might also find Chapter 2 of the Microsoft Patterns & Practices
publication "Application Architecture for .NET: Designing Applications and
Services" helpful. It is available here:

http://msdn.microsoft.com/practices/...ml/distapp.asp

This document discusses passing data through tiers and also MSMQ is
discussed. I suggest also that you take a look at the other P&P documents
available on MSDN:

http://msdn.microsoft.com/practices/

Hope this helps.

--
Regards,

Mr. Jani Järvinen
C# MVP
Helsinki, Finland
ja***@removethis.dystopia.fi
http://www.saunalahti.fi/janij/

[Jani Järvinen [MVP]]

Cable,

I want to build a webservice where I can call it from my web application
when a user triggers the event on demand.

Given your situation, an asynchronous queue is definitely what you need,
however you could also find othe solutions like worker threads interesting.

Luckily .NET supports Microsoft's Message Queue (MSMQ), and it is really a
breeze to use. The problem with MSMQ is that you are tied to Microsoft's
product, but as you are using .NET anyway, this probably isn't an issue.
Take a look at the classes in the System.Messaging namespace. To send a
message, you can use the MessageQueue.Send method, and to read messages, you
could use MessageQueue.Receive method (among others).

You might also find Chapter 2 of the Microsoft Patterns & Practices
publication "Application Architecture for .NET: Designing Applications and
Services" helpful. It is available here:

http://msdn.microsoft.com/practices/...ml/distapp.asp

This document discusses passing data through tiers and also MSMQ is
discussed. I suggest also that you take a look at the other P&P documents
available on MSDN:

http://msdn.microsoft.com/practices/

Hope this helps.

--
Regards,

Mr. Jani Järvinen
C# MVP
Helsinki, Finland
ja***@removethis.dystopia.fi
http://www.saunalahti.fi/janij/