Okay, I basically agree with you. I'll take out
the check for errno and just have recv() == -1
be considered a recoverable error (i.e: retry it).
However, I disagree with making the retry in a
loop for RETRIES times. This is because if one
retry fails, this means this error condition may
not be recoverable without any human interventions.
What is the point of retrying more than once?
My goal is not to wait for TC to come back up
or to wait for TC to be in a good state. My goal
is, if TC is in a good state already, why tell
the caller that it's an error.
Opinions?
shinta
> -----Original Message-----
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 08, 2001 5:12 PM
> To: [EMAIL PROTECTED]
> Subject: RE: FW: problem w/ ajp13 - if Tomcat is shutdown
>
>
> >Okay so this means, you would prefer my proposed solution #1?
> >That was my inclination too.
>
> Proposed solution #1 without the errno check.
>
> My idea :
>
> get the service code in a loop
>
> for (i = 0; i < RETRIES; i++) {
>
> if (send_request() < 0)
> continue;
>
> if (read_reply() == 0)
> break;
> }
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
