Even if modifying the context on the fly is difficult, it should be configurable IMO just as sockets are, before first use.
-Pieter Sent from my Android mobile phone. On Jul 8, 2010 1:25 PM, "Matt Weinstein" <[email protected]> wrote: Folks, The decision to take max_threads out of the API is biting (me) in the following sense: - We have a controlled environment: regression testing is required when source code is changed. This means that I have to build a test suite, and non-standard users can't rely on the community to help debug this change. Also, if my thread requirement increases, it requires a rebuild and reinstall (not to mention retest). IMO, it would be wonderful to re-add this as an API call to modify a context on the fly, and perhaps change the default to some small number (e.g. 50 threads?) so the API call is put to good use :-) RSVP, Thanks, Best, Matt _______________________________________________ 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
