ordinarily, i would favour this (being a standards geek). but here, there is no established base and a small population. and its easy to get new stuff out.
make the protocol lean and clean, and use the bind address to let users pick which interface they want. On Nov 15, 2010, at 2:40 PM, Mikko Koppanen wrote:
Maybe a sensible approach would be to have two (or more) unused bytes after impact and type so that the protocol can be extended later without affecting backwards compatibility. This way people don't need to change the transport to accommodate for changes in the logging protocol. -- Mikko Koppanen _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
------------------ Andrew Hume (best -> Telework) +1 623-551-2845 [email protected] (Work) +1 none currently AT&T Labs - Research; member of USENIX and LOPSA
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
