[dcc2] list/get

[Dan Smith]

>
>Yes, it could be done too. But I think that LIST is just an easier way.
>MULTI could be an alternative option.

Hi Szymon, yeah I understand that point, especially since many people use 
console based clients.  I guess thing brings up a few questions if we are 
going to tackle defining a list/get mechanism.

1.  Where should we implement LIST/GET, as a CTCP or in DCC2?  In CTCP, 
after it has been established which file is to be transferred, DCC2 
negotiation could take place as to how it will be downloaded?

2.  Will there be a standard output of LIST that is machine readable?  And 
if so, will it specify some kind of file handle that can be used with the 
corresponding GET request?

3.  For clients that allow multiple file get/list via MULTI, how should a 
request be initiated?  A type=ircfilelist or something along those lines 
seems to fit the pattern we have been talking about.  This extra type would 
be necessary since the receiving client is requesting that offering client 
send a shared file list, which is opposite of the type=ircfile request.

ideas?

Dan


---------------------------
Dan Smith
+1 608-213-2867
Algenta Technologies, LLC