[dcc2] Multi file sends

[Mark Cilia Vincenti]

I agree with using XML, but maybe we could use XML standards whilst
allowing it to be easier to parse for whoever's making a home-built XML
parser

How about this?

<sendfile type="multi-part" senderID="userJoe" enctype="plain">
	<file name="File1.txt" size="113427" permissions="755"/>
	<file name="File2.txt" size="2293" permissions="777"/>
</sendfile>

Instead of this?

<sendfile>

	<type>multi-part</type>
	<senderID>userJoe</senderID>
	<enctype>plain</enctype>

	<file>
		<name>File1.txt</name>
		<size>113427</size>
		<permissions>755</permissions>
	</file>

	<file>
		<name>File2.txt</name>
		<size>2293</size>
		<permissions>777</permissions>
	</file>

</sendfile>

-----Original Message-----
From: dcc2-bounces at dcc2.org [mailto:dcc2-bounces at dcc2.org] On Behalf Of
Phoenix Fyrestar
Sent: 27 April 2004 12:45
To: DCC2 Working Group List
Subject: Re: [dcc2] Multi file sends

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.

What about using a subset of XML, with set definitions for a few common
file 
attributes.  This shouldn't be too much harder to grok than a set of
tokens 
anyway.

My personal idea of how to impliment this would be to first send an xml
or 
xml-like meta file that would contain information about the files.  It
might 
look something like:

<sendfile>

	<type>multi-part</type>
	<senderID>userJoe</senderID>
	<enctype>plain</enctype>

	<file>
		<name>File1.txt</name>
		<size>113427</size>
		<permissions>755</permissions>
	</file>

	<file>
		<name>File2.txt</name>
		<size>2293</size>
		<permissions>777</permissions>
	</file>

</sendfile>

If something like that is unacceptable,  what about prepending a custom
binary 
header to the top of each file which would be read by the recieving
client 
and then deleted.
This way instead of defining all of the files at once, each file could
merely 
give information about the next file in the queue, sort of like creating
a 
linked list with the files.
	

On Monday 26 April 2004 03:22 pm, Jeremy Iverson wrote:
> Hello,
>
> A few people have mentioned that they don't like the idea of using XML
> to describe the files being sent during multi transfers, since that
> means clients would then need to have an XML parser. I was wondering
> if anybody had ideas for any other formats? I think it has to be
> something more than just
>
> FILE ID "FILE.EXT" "DESC" SIZE CRC
>
> as was suggested on another forum. That simple format doesn't allow
> for extensibility (say, adding meta data about the file like
> permissions, as Timo suggested).
>
> I guess using a token system, similar to how negotiation is done,
> would be one way of doing it. Any thoughts?
>
> Cheers,
>
> Jeremy
>
> _______________________________________________
> dcc2 mailing list
> dcc2 at dcc2.org
> http://six.pairlist.net/mailman/listinfo/dcc2

_______________________________________________
dcc2 mailing list
dcc2 at dcc2.org
http://six.pairlist.net/mailman/listinfo/dcc2