In your previous note you mentioned
looking at code in HTTPAPI, but I am not sure what code exactly to look
at. Maybe a better approach is to say something like:
"This is what needs changed"
and then point me to the similar routine or code snippet in HTTPAPI that
could perhaps guide me.
I'm open to any approach really. I'd
just like to fix this and share the solution when I get it figured out.
Scott Klement <sk@xxxxxxxxxxxxxxxx> Sent by: owner-ftpapi@xxxxxxxxxxxxx
01/25/2006 12:20 PM
Please respond to
ftpapi@xxxxxxxxxxxxx
To
ftpapi@xxxxxxxxxxxxx
cc
Subject
Re: TIMW Issues in FTPAPI
Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>
What sort of information ("bread crumbs") are you looking for,
Brian?
---
Scott Klement http://www.scottklement.com
On Wed, 25 Jan 2006, Brian Eckenrod wrote:
> Hi Scott and list. Some time ago I spoke a bit on the mailing
list about
> an issue we are seeing with FTPAPI when it tries to open a data connection
> and fails and the job hangs in a TIMW state. The initial control
> connection of the FTP works well and the time-out parameter there
works
> perfectly when we get no response. It is on the data connections
for
> directory listings and so forth that we see the issue. We'll
see in our
> log the directory list was requested, but then the log stops there
and the
> job stays in a TIMW forever.
>
> I believe you mentioned we'd need to do something similar to some
code in
> HTTPAPI to allow for a time-out on the data connections. I am
willing to
> work on this (unless someone has already solved this), but I was hoping
> you could drop a few more bread crumbs for me to started on the changes.
>
> Thanks much,
> Brian
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubsribe from the list send
mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------