Am 29.10.2012 um 18:03 schrieb Rafael Schloming:

 think controlling whether or not the application is required to ack at
the subscription level might be a bit weird since you might or might not
need to ack a message depending on where it has come from and that could be
error prone/confusing.

SwiftMQ is doing it this way:

More here:

Andreas Mueller
IIT Software GmbH, Bremen/Germany

IIT Software GmbH
Fahrenheitstr. 1, D28359 Bremen, Germany
Tel: +49 421 2208-166, Fax: +49 421 2208-167
Amtsgericht Bremen, HRB 18624, Geschaeftsfuehrer: Andreas Mueller
Steuernummer: 71/572/04100, VAT: DE199945912

Reply via email to