"adrian@jboss.org" wrote:
In short, if you want this semantic use 2PC.
There is no point building something complicated which is eventually
going to boil down to something more intensive than tranaction logging
anyway!
"timfox" wrote:
I think this is less intensive than tx logging since we only have to log the id rather than the entire tx state, also we don't have the extra client->server call for the prepare.
"adrian@jboss.org" wrote:
Also, this is an additional overhead for people that deliberately
didn't select this QoS because they don't need it..
Another thing we could do is to provide duplicate message detection only for the lifetime of a particular session.
The user could create a session with a special parameter, and then the server would ensure no duplicates were sent by consulting a cache of ids in memory.
Since it's in memory no persistence would be required, basically it would just be an extra hashmap lookup.