> > just remember that calls to generators (i.e. the resultant generated
> value)
> > is outside transaction control - the generation of values has
> nothing to do
> > with transactions - they are merely serialised responses to calls in a
> > queue.
>
> Yes, I know. But I was looking for an explanation, why when there are
> several clients asking for a new counter values (via table row data,
> no real generators), one client gets several values in a row and the

what do you mean by "via table row data, no real generators"?
use generators don't use row data
Alan

> others have to wait. Though every call for a new counter value starts
> a separate transaction.
> But when I think about it, it must be of course the "sleep" of the
> other clients after having got a deadlock on the previous attempt.
>
> Maybe I have to implement something like a sleep also after several
> successful calls. So that others also get a chance to generate values.
> Or, as I alreay mentioned in a previous post, I have to implement some
> kind of queuing mechanism. But how would/should I do this?
>
> --Heiko