o separate the payload.
Cheers,
Lei
On Mon, Oct 30, 2023 at 11:58 PM Brett Viren wrote:
> Lei Jiang writes:
>
> > While putting together my code, I find it a bit hard to keep the
> implementation simple and efficient. For
> > example, the routing IDs are separated by empty fram
roxy being single threaded, I think that's a must?
As the stable versions don't support accessing sockets from different
threads, the bridging code of any 2 sockets must run in a single thread.
Cheers,
Lei
On Thu, Oct 26, 2023 at 1:17 AM Brett Viren wrote:
> Lei Jiang writes:
>
>
ll proceed with my experiment and report back.
Cheers,
Lei
On Mon, Oct 23, 2023 at 3:37 AM Brett Viren wrote:
> Hi again,
>
> Lei Jiang writes:
>
> > The MDP pattern is very interesting but I can't use it in my case. I
> > am aiming to share data and resources inside a pro
Hi,
I hope someone can kindly give me a point in the right direction.
What I want to achieve is to have a thread pool with a bunch of REP sockets
in each thread to handle requests. A ROUTER socket binds to the server
address:port. A DEALER socket binds to an inproc address. All REP sockets
over its
> lifetime then you may run afoul of the thread non-safety of the
> (non-draft) ZeroMQ sockets. This problem can be solved by switching
> from ROUTER/DEALER based MDP to one that uses the draft SERVER/CLIENT
> sockets (which are safe call from multiple threads). If this pr
Hi Brett,
Sorry for the late reply!
On Fri, Nov 3, 2023 at 12:40 AM Brett Viren wrote:
>
> > A long multi-part message could potentially lead to embarrassing
> > situations quite easily. Even when the proxy code is fast, if
> > something gets stuck in either the request or the response, for
>
Pardon me for the noob question!
Does libzmq support GSSAPI on Windows/MSVC? It seems although both
auto-conf and CMake are available, CMake is the only choice on Windows for
MSVC build. But then the CMake file does not have GSSAPI so the only way to
have GSSAPI is to use auto-conf.
Cheers,
Lei
