I am in favour of this idea as well. Also, releasing stable builds to central would be a major plus. I'd be more than happy to donate my time for this effort.
-Trev On Sun, Feb 3, 2013 at 1:02 PM, John Watson <jkwat...@gmail.com> wrote: > On Sun, Feb 3, 2013 at 4:57 AM, Pieter Hintjens <p...@imatix.com> wrote: >> >> I'd encourage you to look at CZMQ and at least use some common >> >> terminology, if you don't map to similar classes. The key features >> which help a lot are: >> >> * message = list of frames >> * attached threads, connected by 'pipes' >> * automatic closing of sockets when context is destroyed >> * context-level linger option >> >> I'm also thinking of writing a class to hide zmq_poll and do that more >> neatly, e.g. manage tickless timers automatically. > > > Excellent ideas. I'm pretty much a zeromq newb, still working through the > guide. Initially I was quite turned off by the java APIs, which is why I > want to make them more idiomatic. > > Anyone else using the java APIs (either jzmq or jeromq) who can provide me > pain points from in the trenches will definitely help with the API design. > > My plan is to do this incrementally. First, I'll work on "modernizing" the > existing API (get rid of int flags, use Collections instead of arrays, make > it more OO, etc), then, once I have a better handle on the bigger picture > (and have studied CZMQ), I'll start layering higher level abstractions on > top. > > If anyone has suggestions or ideas, please let me know. You can also follow > along on my progress in my jeromq fork on github. I'm jkwatson over there. > > Thanks, > John > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
