You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lifo() flavor was introduced after misinterpreting a requirement, since clarified in #87.
I don't think it is actually that terribly useful to serve pending acquire() in a LIFO order.
If you have an actual use case for LIFO order of acquire (and not of idle resources), please comment on this issue.
As a reminder, the lifo() flavor means that when the pool is empty and no more resources can be created, an acquire is parked in a stack instead of a queue. And so, the next time a resource is released, the most recently parked acquire will be unparked and served.
The text was updated successfully, but these errors were encountered:
Motivation
The
lifo()
flavor was introduced after misinterpreting a requirement, since clarified in #87.I don't think it is actually that terribly useful to serve pending
acquire()
in a LIFO order.If you have an actual use case for
LIFO
order of acquire (and not of idle resources), please comment on this issue.As a reminder, the
lifo()
flavor means that when the pool is empty and no more resources can be created, anacquire
is parked in a stack instead of a queue. And so, the next time a resource is released, the most recently parkedacquire
will be unparked and served.The text was updated successfully, but these errors were encountered: