[dcc2] Multi file sends

[Dave Johnson]

Riley White writes:
> 
> On Apr 26, 2004, at 3:44 PM, Phoenix Fyrestar wrote:
> 
> > I personally think that using XML is one of the better possible 
> > solutions.
> > While I understand the reluctance to do this because it would require 
> > an XML
> > parser, I think that any good solution would end up comming back to 
> > something
> > XML-like anyway.
> 
> I honestly don't understand why XML could be considered a bad thing 
> here. Some sort of format is going to have to be defined, and why not 
> XML? For those of us that don't want to link to XML libraries, we're 
> really only dealing with one specific format of data so it can be 
> manually parsed just like any other solution will have to be. For those 
> of us that don't mind using XML libraries, we have that choice. Manual 
> parsing of XML conforming to a known schema may be a little more 
> difficult than whitespace delimited strings, but, speaking as somebody 
> whose had to do it on a couple of occasions, it's not too bad.
> 
> --Riley

Can't the multi-mode file simply contain the same application tokens
as the publication message (one file per line) such as:

ID=1 Filename="file1.txt" Size=3413 Desc="blah 2"
ID=2 Filename="file2.txt" Size=3423 Desc="blah 2"
ID=3 Filename="file3.txt" Size=3433 Desc="blah 2"
ID=4 Filename="file4.txt" Size=3443 Desc="blah 2"
ID=5 Filename="file5.txt" Size=3453 Desc="blah 2"
ID=6 Filename="file6.txt" Size=3463 Desc="blah 2"
ID=7 Filename="file7.txt" Size=3473 Desc="blah 2"

The responce could even be similar to an accept message:

ID=7 Offset=2000
ID=4 Offset=1000
Complete

The reason I propose this is that any client is going to need to parse
a DCC2 CTCP message, why not share the same syntax and parser between
CTCP delivered messages and messages from a multi file.  This also
would mean everything that can be done through the multi-file
interface can be done through the single-file CTCP interface.


-- 
Dave