I just found the proton-demo repo in Github myself and then noticed this post.
Good examples and thanks Rafael for putting in the work to write them for folks like me who are struggling to comprehend proton-j and how to actually use it. I very much appreciate it. I have one question though: in your demo, you have developed nine rather generic classes/interfaces (AbstractEventHandler, EventHandler, Events, Driver, FlowController, Handshaker, Message, Pool, Router) which seem to establish some good usage patterns. However, they also seem to be essential in order to really use proton-j and hence shouldn't they become part of the proton-j library? -Uli -- View this message in context: http://qpid.2158936.n2.nabble.com/Proton-tutorial-synchronous-request-response-tp7613826p7614772.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
