The assumption of every job being the same size and requiring the same expertise is correct. The jobs are simple to reply to a request. So I think this round-robin approach should work. Can you elaborate a bit more on how to implement?
ZAID ----- Original Message ----- From: "Bostrup, Tore" <[EMAIL PROTECTED]> To: "ActiveServerPages" <[EMAIL PROTECTED]> Sent: Wednesday, August 28, 2002 9:43 AM Subject: RE: Rotation > Assuming every job is the same "size" (location, time, expertise, and effort > required, etc.) and if all users work at the same speed, a round-robin > approach *might* work. In reality, things usually aren't that simple. > > Why not use the concept of a queue of (similar) jobs for a role, and have > user request the "next job" from "their" queue (based on their > role/position/location) when they are ready for it? > > HTH, > Tore. > > -----Original Message----- > From: Zaid Abdur-Rahman [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 28, 2002 9:33 AM > To: ActiveServerPages > Subject: Rotation > > > Hello All, > > I have an Access tables of users that is used to assign to jobs. What I am > trying to accomplish is to rotate through the users selecting as individual > jobs come in. What is the preferred.... best, way of handling the rotation > of users? > > Thanks for the time and knowledge. > > Zaid Abdur-Rahman > [EMAIL PROTECTED] > > > --- > You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] > To unsubscribe send a blank email to > %%email.unsub%% > > --- > You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] > To unsubscribe send a blank email to %%email.unsub%% --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
