Hello Joe,
No solution to the failing "socket::large_writes" test yet, but I've
narrowed the culprit to the "ne_sock_read()" function.
It fails for me in a peculiar way. Up to the message size of 65904
bytes it works OK. For N of 1<=N<=120 the received message of
65904+N bytes has N bytes of stale data at it's end and the
"unexpected data: [got] vs [should be]" is printed out. If N is
bigger still - the "ne_sock_read()" fails immediately and the
"broken pipe" is reported.
I think it's down to the way the buffering happens on QNX4.
I wonder why the initial LARGE_SIZE of 123456 bytes works for the
"socket-ssl" test. The value is obviously chosen "out of thin air",
while my 65904 "breakage point" (I speculate still) may be somehow
related to the "lo0"'s MTU (which is ~32790, do not remember
exactly). I'm curious how the test would work over the "en1"
interface with the MTU of 1500...
Hope to find the bulletproof solution. Bebakson...
By the way, I could not find where you actually define the "sread()"
and the "swrite()".
All I can see they are present in the "struct iofns {}"
Please comment.
--
Best regards,
Anthony mailto:[EMAIL PROTECTED]
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
