Why do we have people writing patches for symptoms? if the developer
is not keen enough to actually figure out EXACTLY what is causing the
problem, it is doubtful this same developer should be submitting code
to "fix" it.
Figure out exactly what is causing YOUR problem and then divulge that
- then the community at large can diagnose a proper fix. Simple wait
and retry systems are always fragile (how long to wait? how many
retries before failing?) and usually VERY site specific (hardware
speed, etc.)
On Sep 13, 2006, at 3:29 PM, Doron Cohen wrote:
eks dev <[EMAIL PROTECTED]> wrote on 13/09/2006 13:09:42:
would be nice to accept it. Enough people burned
their fingers on this one
<[EMAIL PROTECTED]> wrote on 13/09/2006 12:52:00:
I've hit this exact issue during development - it's truly
an annoying issue that a simple sleep/retry
loop should resolve.
Actually this is what the current patch attempts for
(FSDirs_Retry_Logic_3)
- did you get a chance to try it?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
