Re: newbie question about fork/pipe/stdin/stdout
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Sun, 28 Oct 2007 01:06:35 -0700
On Oct 26, 3:14 pm, vladimir.plotni...@xxxxxxxxx wrote:
put "wait" after read partially help me.
so, one "big" message passed to child and comes back.
But in some cases (toooooooo biiiiiiiig messages) child will output
any data to stdout. so, my program was locked on "while(!feof())".
Your proxy should make forward progress any time it can. Waiting for
one thing to finish before starting another is a recipe for disaster
if something else waits for the second thing to finish before
finishing the first.
DS
.
- Follow-Ups:
- Re: newbie question about fork/pipe/stdin/stdout
- From: vladimir . plotnikov
- Re: newbie question about fork/pipe/stdin/stdout
- References:
- Re: newbie question about fork/pipe/stdin/stdout
- From: Alex Fraser
- Re: newbie question about fork/pipe/stdin/stdout
- From: vladimir . plotnikov
- Re: newbie question about fork/pipe/stdin/stdout
- Prev by Date: Re: web server design
- Next by Date: Re: looking for small SMTP lib?
- Previous by thread: Re: newbie question about fork/pipe/stdin/stdout
- Next by thread: Re: newbie question about fork/pipe/stdin/stdout
- Index(es):
Relevant Pages
|
