> I will, however, be spending time at work on the stuff to recognize
> broken server handling of the REST command for offsets above 2 GB. I'm >
going to add that as an additional part of this current patch, since it >
doesn't really apply to anyone who isn't also concerned about large
> files (well, at least, as far as I've seen -- all of the servers I've
> talked to support up to 2 GB REST just fine...).

Just a suggestion about that. I think this would be best done as a
CURLOPT_*. Meaning I'm thinking something like how there is the
CURLOPT_HTTP200ALIASES. I'm just thinking, it seems like a bad idea to me to
have something like this, which is essentially going to be a hack, as the
standard way an ftp resume is parsed. Something like
CURLOPT_FTPRESTART2GBLIMITCHECK or something like that, just that way this
code (which seems like it could *possibly* cause some problems since all
servers tend to use different text strings) is only executed if the client
programmer wants it to be rather than the default.

Just my 2 cents though.

Dominick Meglio

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Received on 2003-12-15