[dcc2] Multi headers + metadata

Craig Edwards brain at winbot.co.uk
Wed Apr 28 15:00:55 EDT 2004


if this is the case the simplest encryption and simplest compression methods should be the manditory ones, for slower machines and small-memory machines such as PDAs etc.

e.g. blowfish as the minimum encryption type (as this has been proven to work on small-memory model and slow processors) and runlength or huffman as the basic compression type (however this would still be optional as the receiver could still say 'no thanks' to the compression and force the file to be sent uncompressed).

>If I understand what you are saying, we should have something like
>
>	encryption=<encryption type>
>	compression=<compression type>
>	misc=<thing1>
>
>and at first it really sounds like a good idea, but I think we should 
>standardize on a single type of compression and maybe a couple of types of 
>encryption, otherwise we could have support fragmentation with one client 
>supporting only compression type x and another supporting only compression 
>type z, and a third supporting a, b, y and z.
>I think of course making it extensible so clients can add additional features 
>is a good thing, but any additional compression, encryption, etc. modes 
>should be outside the scope of what is defined as encryption or compression 
>in the standard.  If we don't then it ends up that either every client has to 
>support many compression modes (bloat) or they don't interoperate well 
>(making the feature pretty much useless)
>
>On Wednesday 28 April 2004 11:19 am, Mark Cilia-Vincenti wrote:
>> I think there should be fields for compression, encryption etc so users
>> put in module names that they have and if they match they use the
>> compression for example. Also this should be flexible so as to allow
>> anything else we might have missed. Eg someone might make a module which
>> would require you to authenticate with a 3rd party before you actually
>> get sent the file.
>>
>
>_______________________________________________
>dcc2 mailing list
>dcc2 at dcc2.org
>http://six.pairlist.net/mailman/listinfo/dcc2



More information about the dcc2 mailing list