My initial thought on seeing Phil's posting was that it might be a server setting and thus not something one can control at the client.
I thought this because a couple of weeks ago I stumbled upon a discussion where SSH (for some user) was creating a new connection for each command sent to the server. It was fixed by changing a server setting so that SSH re-used connections. At least that's how my memory of the discussion. Bernard On Wed, Apr 15, 2009 at 4:23 AM, Sarah Reichelt <[email protected]> wrote: >> While using libUrlFtpUploadFile to upload a bunch of files to a server, I >> find that libUrlFtpUploadFile opens a new socket for each upload. Even using >> a callback message to start a new one when the current one finishes, I get a >> "max number of connections" message back from the server when the server's >> max number is reached. After this, the next few upload attempts fail due to >> max number of connections; then as the open connections time out, new files >> can successfully upload again. > > I had this problem with a particular server. I always get the new > connection with every command, but not all servers mind this. > My solution was to use libURLSetFTPStopTime and set it to a very small > number. This supposedly allows re-use of an existing connection, but > in my experience all it does it keep one open while still opening > another. If you set it to a very low number, then connections will > close more rapidly, so you should not reach the maximum number of > connections allowed. > > HTH, > Sarah > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
