[zeromq-dev] context

Ilja Golshtein ilejncs at narod.ru
Thu Aug 26 11:51:33 CEST 2010


26.08.10, 13:28, "Martin Sustrik" <sustrik at 250bpm.com>:

> Hi Ilja,
>  The context is just a place to store "global" variables. Using real 
>  global variables in a library is dangerous, thus the context.
>  So the rule of the thumb is: Use one context per executable or library.

Does it mean inproc communications are always direct and no auxiliary thread is involved?

Does your interpretation of context as a global variable imply there is no connection between context and inner thread pool? I had an impression a context owns connection pool.

>  The argument is just the size of the thread pool used to handle the I/O 
>  operations. In 99% of cases you want just a single I/O thread.

Do we have an example of rest 1%?
Did anyone ever face a situation one thread was not enough?

The only example comes to my mind is several network cards per a box or may be an advanced card with multiple queues. Something else?

Thanks and sorry if my questions are too insistent - just want to have this thing demystified.

Best regards,
Ilja Golshtein.

More information about the zeromq-dev mailing list