https://bugs.exim.org/show_bug.cgi?id=2130
--- Comment #2 from Simon Arlott <bugzilla.exim.simon@???> ---
(In reply to Jeremy Harris from comment #1)
> The basic issue is that we want to know the full result record from one of
> possibly-many transport procs is identifiable by the transport dispatch
> process.
> Query: do we create a new pipe for each transport proc? If so then a read
> loop will suffice (but sharing one would be a performance enhancement).
I doubt a separate pipe for each transport process is a significant performance
issue. Use a read/write loop so you don't need to worry about buffer sizes.
It can then be converted to an AF_UNIX SOCK_STREAM which will have a larger
buffer size and do a minimal number of reads/writes most of the time, without
running into SOCK_DGRAM/SOCK_SEQPACKET maximum message size issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
