Click here to Skip to main content
15,881,744 members
Please Sign up or sign in to vote.
2.00/5 (1 vote)
See more:
Background: My experience has been writing "standard" windows services as well as standalone applications. I have also done quite a bit of ASP.NET.

I am in need to write a RESTful web service that acts as a middle man between clients and back end managers. The client sends a login notification to the service. Service would then queue the job. That part based on my research I think I have a handle on (in theory).

I could easily have the web service just queue to a database and write a second "standard" service process that queue. But I don't know if that is the proper design or not.

Is it possible/acceptable/bad practice to have a web service have separate queue processing threads from the web components? Or should this challenge be better solved by a web service for queuing and a standalone service to process the queue?

Thanks very much for any suggestions/direction.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900