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
Hi Sarah,
Rather than gambling and waiting for a timeout to occur and, assuming there
aren't any other sockets open for other purposes, couldn't Phil just issue a
resetAll in his uploadEnded command? This forces the close of all sockets
and a reset of everything in liburl. Otherwise, a close of
Howdy -
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
Hi Phil,
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
I think that using a callback handler you can detect the 100% complete
message from the server,
then issue a 'QUIT' to close the connection immediately, then after
getting the 'GOODBYE', start the next upload.
I have not done this in practice that I know of (accidents do happen
and things
Hi Jim B Jim A,
Thanks for the replies.
Actually I'm using libUrlFtpUploadFile because some of the files are
movies (some 100mb), so I don't want to use a blocking command.
The more I think about this, the more I believe it's a libUrl bug. If
socket reuse works for download (which I
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
Thanks Sarah.
Sarah Reichelt 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
