On 03/30/2010 01:06 AM, Kamil Dudka wrote:
On Tuesday 30 of March 2010 05:09:44 Ben Greear wrote:
It seems to me that it would be best to just allow passing the file list
back to the user and let them parse it and then make individual
requests for files as desired.
Parsing of the file list is protocol-specific, though not properly
standardized AFAIK. I think such ability of libcurl may be useful
for some class of applications.
What's the advantage of putting all of this into libcurl?
Though the patch is not tiny, major part of the code is the mentioned
parser. As for the public libcurl API I don't think it is that
intrusive. Beyond the specific task, it introduces a new interface
for processing more objects per one URL, which may also be used by
some other protocols in future.
Well, it's certainly not my decision, but it still seems like this should
be in user-code, not in the library.
As it happens, I've been working on returning listings for POP and IMAP,
and those are going to be very different from the info you can get
from ftp. I'm not sure it can really be generalized.
Thanks,
Ben
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
