qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cliff Jansen" <cliffjan...@gmail.com>
Subject Review Request 26075: Document Proton-c IO restrictions for 0.8 release
Date Fri, 26 Sep 2014 06:46:14 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for qpid.

Bugs: PROTON-668

Repository: qpid


This describes my best guess of balancing convenience for the developer versus performance.
 Ultimately, with the exception of stickiness between completion ports and sockets, which
prevents moving a socket between or out of a pn_io_t, any Posix behavior can probably be mimicked
in Windows, but at a performance penalty.

With these restrictions, third party event loops are supported.  Proton event loops can also
accommodate external non-sockets if that is useful (if dispensed with, that makes Windows
code easier).  Multi-threaded IO as currently used in Dispatch is also supported.

It is worth noting Bozo's points that the interface doesn't always make sense for multithreaded
ops: pn_io_error() and pn_io_wouldblock().

Finally, it should be noted that the Windows code has some way to go to satisfy the above,
but understanding the intended supported capabilities needs to come first.


  http://svn.apache.org/repos/asf/qpid/proton/trunk/proton-c/include/proton/io.h 1627716 

Diff: https://reviews.apache.org/r/26075/diff/




Cliff Jansen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message