I have a .NET 2.0 web application on shared hosting environment which is hooked to a SQL Server 2005 database.
I want to give my users an instant response and let a thread handle the processing in the background. The design in place does the following:
For each user who logs into site this will happen
1. User logs into site and creates X messages.
2. Write each message to a record to a MessageQ table for this user in database
3. Return control to user and start a thread which reads MessageQ entries for this user and processes.
My question is.. ... Does this design look ok?
Each user accessing the system will create a thread for their messages so potentially N users could have N threads all accessing the MessageQ table at the same time.
That is my concern.