Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • A message queue would be a sensible approach. I was wondering if, when implemented I might have problems with multiple threads making the same query repeatedly and slowing the server down. This should help mitigate that. As a side note, the bit field was supposed to be "checked out" field. Commented Aug 27, 2013 at 20:35
  • I dont think a true/false can handle both a selected and checked out status as there are 3 states - unprocessed, being processed, and processing done. Otherwise if the server goes down, you may miss items in the queue if they are prematurely marked as completed. Thus separating them into two columns, one for processing state, and for checked out state. Commented Aug 27, 2013 at 21:10
  • see edited answer for other approaches Commented Aug 27, 2013 at 21:15
  • I thought about the single thread approach but I don't think it is suitable because the processing the thread is required to do requires access to Internet resources where the latency is unknown therefore the thread could be waiting some considerable time. There was also a misunderstanding over the "checked_out", I didn't mean there were three states but I also misunderstood your comment. I understand now what you mean about a "checked out" and a "processed" flag. Commented Aug 28, 2013 at 6:59