Tom Hobbs wrote:
I know of at least one company which uses Outrigger specifically
because of it's fortuitous FIFO behaviour. I'm trying to encourage
them to move from the Jini 2.1 code to the River release and losing
the FIFO-ness might be an issue for them.
And yes I know, the spec doesn't specify FIFO, like I said, they
needed a FIFO space, and Outrigger "just happened" to behave like
that.
That confirms my suspicion that FIFO-ness is a useful property. I note
that Gigaspaces has optional support for FIFO.
My quick changes to try to fix the current bug will preserve it. If the
long term design loses it for flat-out performance, we should make it
available on a configuration basis.
Patricia