Stomp uses named transactions so that many transactions can concurrently occur at the same time.
The client specifies the name and it is unique to that client.
then you can ack or send using the transaction
hello queue a!
Would "undo" the ack and send
It would be helpful to have a little more details on what an implementation needs to handle as far as transactions go. Perhaps much of this can be left up to implementation developers; however, I can imagine that users would find some of this clarified here. A few specific questions I have (I apologize in advance if these are naive):
Powered by a free Atlassian Confluence Open Source Project License granted to Codehaus. Evaluate Confluence today.