On Fri, Nov 19, 2010 at 9:21 AM, Martin Sustrik <[email protected]> wrote: > On 11/19/2010 05:48 PM, Dhammika Pathirana wrote: > >> -1 for auto buffer resizing. >> This is bound to go gaga anytime, and possibly has a remote trigger. >> >> Different option is to send cmd_t struct pointers. It'll give about >> 16K commands with 128K >> socket buffer. But this will require malloc'ing cmd_t structs, or we >> can use a ring. > > That can be optimised. No problem. The hard part is synchronising the state > of internal fds (mailbox_t) with the queue of command_t's in such a way when > the fd is signals POLLIN iff there's a command in the queue. > > Seems easy, but it's actually pretty hard. Maybe unsolvable? In any case, > nasty race conditions tend to emerge. My feeling is we are getting to the > edge of what can be done via POSIX API. >
What if we make write a blocking call, then it's about making the reader fast. I guess it's not a deadend. Dhammika _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
