On Wed, Jun 06, 2007 at 04:09:01PM -0700, Frank Cusack wrote: > On June 6, 2007 9:01:45 PM +0100 Joe Orton <[EMAIL PROTECTED]> wrote: > >Right - since it didn't open it either. If you want to leave the fd > >open then you can use lseek(fd, 0, SEEK_CUR) or similar to determine the > >file pointer position (before and after) and derive the response length > >like that. > > that doesn't work on a pipe though. > > best solutions i can think of are > > - have a call that can retrieve the content-length, then i know how much > to read() > - set a flag telling ne_get to close the fd > > will you accept a patch for the latter option? i'm trying to use neon > because it's simpler than some of the others, e.g. libcurl. but i need > a reliable EOF indicator.
Why not simply call close() yourself on the write-end of the pipe? Why do you need ne_get() to do it? (and make sure you are also closing the write-end in the child if you are forking, otherwise you'll never see the EOF regardless) joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
