Well it could probably use a tweak. I did not get this completely right but
I wanted to get the code checked in before it ended up sitting on my
computer for a couple weeks. IDBroker tries to keep ahead of the requests
for ids. It checks every few minutes (static final constant) to see if it
should grab more ids. If a request comes in before it has an id ready it
increases the number of ids (QUANTITY) it will grab from then on. This
should be working ok I think, but it might be nice to have some way of
relaxing this quantity.
The main thing that needs improvement is that the IDBroker does not start
storing ids until a request comes in, so the quantity is set based on the
assumed prior load due to QUANTITY and the difference between when
IDBroker's thread last woke up and when the first id was requested. The
NEXT_ID should be incremented according to the quantity of ids grabbed and
stored in memory.
----- Original Message -----
From: Leon Messerschmidt <[EMAIL PROTECTED]>
To: Turbine <[EMAIL PROTECTED]>
Sent: Friday, July 21, 2000 12:19 AM
Subject: IDBroker -> IDTable problem
> Hi,
>
> When I'm using the new IDBroker with id_table the quantity column of
id_table seems to
> change at random. Is this supposed to be like this? The next_id also
gets incremented
> what seems to be random steps.
>
> ~ Leon
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
