On Tue, 21 Jan 2020 at 17:06, Rob Godfrey <[email protected]> wrote: > > On Tue, 21 Jan 2020 at 16:38, Robbie Gemmell <[email protected]> > wrote: > > > On Tue, 21 Jan 2020 at 14:28, Rob Godfrey <[email protected]> wrote: > > > > > > On Tue, 21 Jan 2020 at 14:24, Robbie Gemmell <[email protected]> > > > wrote: > > > > > > > On Tue, 21 Jan 2020 at 11:21, Rob Godfrey <[email protected]> > > wrote: > > > > > > > > > > [... snip ...] > > > > > > > > > > > 6. receiver-options - "auto-accept : Automatically accept deliveries > > that > > > > > are not explicitly acknowledged"... what does this mean - when does > > the > > > > > accept happen, when the message is initially received, or only if the > > > > > delivery somehow goes out of scope? > > > > > > > > For receive calls it would be when received. > > > > > > > > > If there was a listener > > > > (TBD) it would be after that returned. Much the same as existing > > > > clients auto ack essentially. > > > > > > > > > > So... looking through the API design... the only way I see to receive a > > > message is through messaging-handler.on-message. So the idea is the > > > auto-accept means that upon the return from on-message, if the outcome > > has > > > not been set to accepted, and the message has not already been settled > > (by > > > either side) then the outcome of the delivery will be set to accepted. > > > > > > > There are recieve calls on the reciever, see the bottom of > > https://www.ssorj.net/pumpjack/client/receiver/index.html. > > > > > How do you get from the delivery to the message? >
In one case at least, currently delivery.message() > With the recevier.receive call... I'm not sure how the second half of the > description "auto-accept : Automatically accept deliveries that are not > explicitly acknowledged" makes any sense. I don't see how "explicitly > ackowledg[ing]" is even possible. > It isnt, calling receive with auto-accept would be expected to acknowledge immediately at present (unless some other behaviour were defined). The latter bit can only apply to the handler style usage. The text is loosely covering the bases, and was perhaps even copied from previous reactive api bits where auto-accept is an option and no receive style use is possible. > -- Rob > > > > > The messaging-handler stuff is again mostly part of the existing > > reactive bits (in some cases), which indeed work essentially as you > > describe. The idea would be something similar (but obviously narrower > > in operation scope) for the handler configurable in the reciever > > options. > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
