Long process in ASP.NET

[Albert Pascual]

What's the best system for a process that could take a long time, minutes,
hours

a) Creating a webservice that calls a Thread?
b) Creatinga webservice with [SoapDocumentMethod(OneWay=true)]
c) Any better way? without using an external program?

Thanks
Al

[Li-fan Chen]

Hi Albert,

Another way is queuing jobs. MSMQ or Service Broker (SQL Server 2005).

1. Create a job class instance in .NET and assign a unique id to it (GUID,
auto incr in some table).

public class Job
{
string ID;
}

1.1 This class is a great place to put in the criterias required to perform
the long-running task.

2. Track the job. For example: with the Ticket (Job.ID), INSERT TABLE
tblJobs SET Completed = FALSE WHERE ID = @ID

3. When the job is done make sure the job executor updates the completion
bucket to say the job is done.

UPDATE tblJobs SET Completed = TRUE WHERE ID = @ID

4. Until then, give your response page the Job ID. It will refresh (great
place to add an AJAX enabled progress bar) and use that ticket to check
whether the job is done or not in the completion bucket:

With the Ticket (Job.ID), Query for SELECT TOP 1 WHERE Completed = TRUE AND
ID = @ID

Others are welcomed to recommend a better way.

Best regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Albert Pascual" <Al***********@discussions.microsoft.com> wrote in message
news:9E**********************************@microsof t.com...

What's the best system for a process that could take a long time, minutes,
hours

a) Creating a webservice that calls a Thread?
b) Creatinga webservice with [SoapDocumentMethod(OneWay=true)]
c) Any better way? without using an external program?

Thanks
Al

[Li-fan Chen]

Hi,

Just an appendix: you can also peek into the queue to see if the job has
been dequeued. That tells you the job is done as well. Depending on the size
of the queue, it might be worth it to save the DB round-trip.

Best personal regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Li-fan Chen" <ob*******@hotmail.com> wrote in message
news:uE****************@TK2MSFTNGP15.phx.gbl...

Hi Albert,

Another way is queuing jobs. MSMQ or Service Broker (SQL Server 2005).

1. Create a job class instance in .NET and assign a unique id to it (GUID,
auto incr in some table).

public class Job
{
string ID;
}

1.1 This class is a great place to put in the criterias required to
perform the long-running task.

2. Track the job. For example: with the Ticket (Job.ID), INSERT TABLE
tblJobs SET Completed = FALSE WHERE ID = @ID

3. When the job is done make sure the job executor updates the completion
bucket to say the job is done.

UPDATE tblJobs SET Completed = TRUE WHERE ID = @ID

4. Until then, give your response page the Job ID. It will refresh (great
place to add an AJAX enabled progress bar) and use that ticket to check
whether the job is done or not in the completion bucket:

With the Ticket (Job.ID), Query for SELECT TOP 1 WHERE Completed = TRUE
AND ID = @ID

Others are welcomed to recommend a better way.

Best regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Albert Pascual" <Al***********@discussions.microsoft.com> wrote in
message news:9E**********************************@microsof t.com...

What's the best system for a process that could take a long time,
minutes,
hours

a) Creating a webservice that calls a Thread?
b) Creatinga webservice with [SoapDocumentMethod(OneWay=true)]
c) Any better way? without using an external program?

Thanks
Al

[Albert Pascual]

Actually I was looking for something like somebody presses the button on the
webpage and the job starts!

"Li-fan Chen" wrote:

Hi Albert,

Another way is queuing jobs. MSMQ or Service Broker (SQL Server 2005).

1. Create a job class instance in .NET and assign a unique id to it (GUID,
auto incr in some table).

public class Job
{
string ID;
}

1.1 This class is a great place to put in the criterias required to perform
the long-running task.

2. Track the job. For example: with the Ticket (Job.ID), INSERT TABLE
tblJobs SET Completed = FALSE WHERE ID = @ID

3. When the job is done make sure the job executor updates the completion
bucket to say the job is done.

UPDATE tblJobs SET Completed = TRUE WHERE ID = @ID

4. Until then, give your response page the Job ID. It will refresh (great
place to add an AJAX enabled progress bar) and use that ticket to check
whether the job is done or not in the completion bucket:

With the Ticket (Job.ID), Query for SELECT TOP 1 WHERE Completed = TRUE AND
ID = @ID

Others are welcomed to recommend a better way.

Best regards,
-- Li-fan

--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Albert Pascual" <Al***********@discussions.microsoft.com> wrote in message
news:9E**********************************@microsof t.com...

What's the best system for a process that could take a long time, minutes,
hours

a) Creating a webservice that calls a Thread?
b) Creatinga webservice with [SoapDocumentMethod(OneWay=true)]
c) Any better way? without using an external program?

Thanks
Al