On Thu, Jan 26, 2012 at 4:05 AM, Martin Lucina <[email protected]> wrote:
> > It is bad design process to exaggerate the user's requirements into > > absurd extremity and then state there is no simple solution. It's far > > wiser to understand the actual problem people are trying to solve, and > > solve that simply and minimally. > > Given that an API will stick around for a long time, it is good API > design process to extrapolate current and possible future use cases > and arrive at the simplest possible API covering all these use cases. > Is it possible that this API should simply be on a different calls, a zmq_bind_assign or similar, to avoid this clash? This could then work with all transports: tcp/pgm: bind to random port ipc: bind to random free name in system tmp inproc: bind to random free name That can either have a return parameter which gives you the bound address, or it can be passed back via a second argument or similar. Ian
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
