On Thu, May 12, 2011 at 6:26 PM, Henry Baragar <[email protected]> wrote:
> Should the identity of a durable socket be unique for an application, or for > a socket within an application? The documentation simply states that if you set an identity, that is used to associate resources with the socket. In practice, 0MQ holds resources per binding socket, so that sets the limit for uniqueness. In theory, this can change at any time, so the limit is application wide. In further theory, the whole notion of durable sockets may be dropped in future implementations since it's extraordinarily complex in the code, and tends to create brittle architectures. If you must use durable sockets, I'd advise using application-unique identifiers or UUIDs. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
