genman wrote : For durability, SonicMQ supports durability by using persistence on the
client side; MessageProducer.send() persists messages on disk, then delivery happens
asynchronously in another thread. Again, some sort of mechanism would provide flow
control.
|
| For "thin clients", you'd to have to provide some sort of simple
client-side persistence model. A central database wouldn't make much sense. I'm
guessing a "simple" transaction log might work. ("simple" rarely is
though.) There'd have to be some sort of recovery mechanism and callbacks for error
detection...
Yes, this is the "point of sale" scenario. There is a JIRA task about this ...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979733#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...