cshannon commented on PR #1364: URL: https://github.com/apache/activemq/pull/1364#issuecomment-2537496438
One idea I had as another option for 7.3.8 is to only process one message a time. Well technically, this was @tabish121 idea. The spec says that the callback must be processed in a new thread for the async send but it doesn't say that multiple concurrent sends must be allowed. So the sending thread could block and wait for the send to finish and execute the callback before continuing. This of course is similar behavior to the normal sync send that just sends a message at a time and blocks. This is the simplest way to meet the spec (turning it into sync essentially) but the downside is not allowing the throughput of multiple sends at once. We could do something like make the mode configurable with legacy vs compliant mode. If it's legacy it could fall back to the existing async behavior that doesn't meet the spec, and if it's compliant it goes into the mode where it just sends one a time. A future update could be done to make the "compliant" mode better and allow it to handle multiple sends at one by tracking the order. Again, _potential_ option, I'm not sure this is a good idea either but another idea I had. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: gitbox-unsubscr...@activemq.apache.org For additional commands, e-mail: gitbox-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
