Re: Artemis 2.20.0 + Stomp protocol: to Ack or to Nack, that's the question

2022-03-03 Thread Justin Bertram
, > > ER. > > > Enviado do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para > Windows > > De: Justin Bertram<mailto:jbert...@apache.org> > Enviado:quinta-feira, 3 de março de 2022 12:17 > Para: users@activemq.apache.org<mailto:users@activemq.

RES: Artemis 2.20.0 + Stomp protocol: to Ack or to Nack, that's the question

2022-03-03 Thread Edson Richter
do Email<https://go.microsoft.com/fwlink/?LinkId=550986> para Windows De: Justin Bertram<mailto:jbert...@apache.org> Enviado:quinta-feira, 3 de março de 2022 12:17 Para: users@activemq.apache.org<mailto:users@activemq.apache.org> Assunto: Re: Artemis 2.20.0 + Stomp protocol:

Re: Artemis 2.20.0 + Stomp protocol: to Ack or to Nack, that's the question

2022-03-03 Thread Justin Bertram
Yes, STOMP supports a NACK frame. The STOMP 1.2 specification [1] says this about the NACK frame: > NACK is the opposite of ACK. It is used to tell the server that the client did not consume the message. The server can then either send the message to a different client, discard it, or put it in a

Artemis 2.20.0 + Stomp protocol: to Ack or to Nack, that's the question

2022-03-03 Thread Edson Richter
I’m writing a Go client using Stomp protocol. I’ve read all the chapter about Stomp protocol in Artemis Docs. I understand I can’t use transactional Ack as per this paragraph: “The STOMP specification identifies transactional acknowledgements as an optional feature. Support for transactional ac