Yes, quite a few actually for embedded systems. There are quite a few high speed rs422/485 serial interfaces still being developed. The primary reason for doing this is that I already have to define a framing and messaging protocol, and resultant code, to interface with those devices, so I'd rather just reuse the zmq protocol and pull those into the fold so I can interface with them directly through and get all the zmq benefits.
On Fri, May 25, 2012 at 3:41 PM, Pieter Hintjens <[email protected]> wrote: > On Fri, May 25, 2012 at 4:43 PM, Thomas Taranowski <[email protected]> > wrote: > >> For the time being I modified the tty_engine to use inout, rather than >> codecs, but it's not clear to me yet which path is more consistent >> with plan for zmq. > > Tom, the plan is just to make small, safe iterative changes to libzmq. > This is the main reason I didn't port the session changes back from xs > to zmq. So if you're more comfortable modifying the tty_engine, that's > fine. If you prefer to modify the codecs, that's also OK. > > Are there actual use cases for a tty:// transport? (Flashback to 1990 > and serial UART programming...:) > > -Pieter > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
