On 26/10/2015 10:54, Benoit Tellier wrote: [...]
Seriously, I think dropping MESSAGE SEQUENCE NUMBER and returning an error on distributed implementation is our simplest walk-around on this topic... Doing overwise demands to add capabilities to the MessageManager to handle MESSAGE SEQUENCE NUMBER with really tricky code.
The real problem is about deletion because addition can be managed by the atomic row trick and immutable datamodel.
I think we could create a Session row that map MESSAGE SEQUENCE NUMBER to the real messages. Then, for a given session, we never remap things, we only add messages to this row. In case of EXPUNGE, we create a new row that won't be used until a new session is open.
That way, a client can't use a MESSAGE SEQUENCE NUMBER wrongly because it always maps to a given message.
Do you get it ? -- Matthieu Baechler --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
