Daniel To my mind there is a rational need for the MyQueue class - I would place methods here that operate on the whole queue eg empty queue
Also you can implement many different independent queues each with it's own OBJID - separate instances of the MyQueue class Just a comment on ListOfQueue items being held as a List collection I am not sure that this is a good idea a list collection has a limited length (depends on the length of individual items) also if there are many items in the queue I am not sure of the efficency of inserting/shuffling the queue Better IMO is child classes Peter On Tue, 03 Aug 2004 15:45:44 -0400, Daniel Santa Cruz <[EMAIL PROTECTED]> wrote: >Hello all, > >I needed a queue to hold certain information to be processed at a later >time by a different process. So, I started with: > >MyQueue Class: > List of QueueItems > >MyQueueItem Class: > Data for the Item > Timestamp > Processed flag > >Then I noticed that really MyQueueItem Class is also in a way a Queue. >One has the ability to get to the data since it is all stored in the >same SQL table. Is ommiting the MyQueue class a bad idea? Would it be >better to just have that class, and to have to 'push' items in and out >of the queue, so that there is a way to access them directly through OO >instead on haven SQL queries to retrieve them? > >I guess I'm still thinkin in tables... > >Thanks. > >Daniel.
