For anyone interested, I added support for ByteBuffer's in my fork: https://github.com/trevorbernard/jzmq/tree/bytebuffer-api
I wrote a couple simple unit tests that pass. I still have a couple of house keeping tasks left to program but for all intents and purposes, it's done. -Trev On Tue, May 14, 2013 at 8:35 AM, Trevor Bernard <trevor.bern...@gmail.com> wrote: >> What is the purpose of int recvByteBuffer(int flags) ? > > Oops, typo. The return type should be ByteBuffer. You can create a > direct bytebuffer with NewDirectByteBuffer. > >> Will this be a true 0 copy implementation? Or will the buffer still be >> copied within the send/receive call? > > The buffer will still be copied within send/receive. Zero copy is a > different beast. My motivation for a bytebuffer api is to remove > copying in the JNI layer. > >> I'm already looking forward to performance measurement. This looks >> interesting. > > I'll try to get some before and after numbers with various different > payload sizes. _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
