On Wed, Oct 8, 2014 at 4:40 AM, uromahn <ulr...@ulrichromahn.net> wrote:
> 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? > Yes, I intend to pull at least some of them in shortly. (Hopefully for 0.8 RC2.) I think the *EventHandler stuff is pretty much a no brainer for "core" proton-j. The other pieces I would like to pull into a "toolkit" area for components that are useful and should be available, but aren't necessarily the one and only way of doing things. --Rafael