This would be totally from a Messaging Point of View.. not just JMS BTW. Right now there are 2 JMS components that would be cross used from qpid-jms, artemis.. and who knows… Rocket…
- Serders/Serialization integration for Object messages - JMS Connection pool… There’s also the idea of using the Journal on the client. The Journal from Artemis could move here, we would add a JournalQueue which would allow integrating Messaging on the client side. It would be a great component for either Artemis, kafka or anything else that needs a journal. I don’t have any specific ideas now.. but I know of some libraries for Javascript clients, think of Kafka, AMQP… as well that could live here. We could only expand from there.. On 2017-06-21 22:35 (-0400), "John D. Ament" <johndam...@apache.org> wrote: > All, > > There's an ongoing discussion on the ActiveMQ dev list [1] to spin up a > project focused on core, reusable messaging components. The feeling is > that this is outside the realm of ActiveMQ for various reasons and could be > leveraged by various messaging platforms, potentially even building out > some reusability and core protocol support along the ways. > > Knowing that we have some messaging experience within the incubator, I > wanted to prod around a bit to see if there was anyone else interested in a > project like this. > > John > > PS - when I say interested parties, it could be > champions/mentors/contributors or heck even possible TLP sponsors. > > [1]: > https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c373e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
