httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject RE: errnos and buff.c
Date Fri, 18 Dec 1998 20:18:55 GMT


On Wed, 16 Dec 1998, RobS wrote:

> > If you want to use a hard_timeout, then I don't think I can really
> > recommend that too greatly, but you still have to deal with error returns
> > from functions.  Well, you can currently get by without doing so since the
> > SIGPIPE will make things work after a few failed writes but that isn't
> > reliable nor is it a long term solution since it currently causes
> > problems with other sockets that modules may open plus it isn't
> > sustainable in a threaded model.
> 
> Why is hard_timeout bad?  I thought it was one of those neato features
> (aaaaaaaa, times up, your outa here).

Take a look at any library code that does i/o.

Look at the critical sections where they've begun i/o and would be totally
screwed if you longjmp'd out of them.

> What do you expect the threaded solution will look like?

See apache-2.0/apache-nspr/README.NSPR or something like that, I talk
about this.

Dean


Mime
View raw message