Hi Integrin
It looks to me that Job Scheduler could be suitable as it works like a queue
already. No need to reinvent the hot water :) I could safe myself some work
and a lot of testing there.
Anyone more knowledgable about how the Job Scheduler works?
What happens it you put the same service several times inside? Any way to
specify that only one thread should be devoted to one service name?
-----Original Message-----
From: Integrin
Date: 19 април 2012 г. 20:41 ч.
To: [email protected]
Subject: Re: Job scheduler as a message queue
Boris -
Job Scheduler be used for timed invocation of services and perhaps not
suitable for this usecase;
I'm guessing, you need a queue data-structure to hold the registration
requests and a dedicated worker thread clearing off the queue;
- Regards
On 4/19/12, Boris Hamanov <[email protected]> wrote:
Say, a user registers on my site, through a form; I am running a service
that does the registration.
Now suppose 10 users use the form simultaneously and submit their
registration at approximately the same time. My service is called 10
times.
I want to guarantee that one and ONLY ONE instance of my
registration service runs at any given time.
I need that because in my specific scenario each subsequent registration
depends on the previous ones.
Can I make my service asynchronous and use the job scheduler to achieve my
goal?
Thanks in advance ;)
--
Sent from my mobile device
