[DGD]callout order

[Kevin Carpenter]

Works for me.  In any situation where I use callouts, its typically one
per event.  The events are independant of each other so the actual
sequence of execution is irrelavent.

Kevin C.
> 
> I am considering removing some guarantees on callout order as they
> exist now: at present the order in which short-term callouts (integer
> delay <= 127 seconds, including 0) are executed, when the delay
> has passed, is the order in which they were created.  I'd like
> to remove that guarantee: if you start two callouts with a 5
> second delay immediately after eachother, they could be executed
> in any order.  However, they <will> both be executed before a callout
> delayed for 6 seconds.
> 
> What I propose above is already the case for long-term (>= 128 seconds)
> and millisecond callouts.
> 
> This change would substantially speed up DGD on a multi-processor
> system, support for which I will be adding immediately after I
> complete the implementation of atomic functions.
> 
> Comments?
> 
> Regards,
> Dworkin
> 
> List config page:  http://list.imaginary.com/mailman/listinfo/dgd
> 


-- 
Kevin Carpenter
Kevin's Home Page: http://www.monrou.com/kevinc
(Expressing his comments from home in St. Louis, where this message originated)

List config page:  http://list.imaginary.com/mailman/listinfo/dgd