On Monday 10 July 2006 14:45, Bruce Stephens wrote: > How about makeing the chunk size settable using a new command (leaving > the default as it is)? Or set the default to 1M (or BUFSIZ, or > something), and then clients that would deadlock have a way to set it > to something smaller. > > I'm not sure whether 1M would cause a problem. I wouldn't rule it out > for some simpler clients (using synchronous I/O and polling various > inputs).
After thinking a while about it, it is no longer clear to me, why there is a need for chunked output *at all* ... The reading side of a pipe can always read the data in arbitrarily (and independently of the sender) sized packets, even when using synchronous I/O, by simply specifying the size in the read() call. The sender must of course check how many bytes of it's write() call actually got written. - Thomas -- Thomas Moschny <[EMAIL PROTECTED]> _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
