[dcc2] MultiFile Transfer Headers

[Jesse McGrew]

peter green wrote:

>file permissions are completely meaningless crossplatform and pretty
>meaningless between different machines of the same type
>
>the NT system only has meaning at all within one NT domain (or one machine
>in a non domain environment)
>
>the unix system has some meaning cross system but the owner and group are
>likely to be different on the target than on the source and preserveing them
>could lead to significan't security issues
>  
>
If file permissions are included at all, they should be minimal... e.g. 
no more than "executable" and "private". The client can decide how to 
translate between the platform's security options and those basic 
permissions. Any more detailed file permissions are unlikely to be 
portable, and they can already be handled by putting the file inside an 
archive.

I'm not sure that we even need to include file permissions, though. When 
would a recipient really need to know whether the file he's receiving is 
supposed to be executable? If he's expecting a program, he can set the 
bit himself, and if not, his client shouldn't set the bit for him. The 
only one I can see a use for is a "private" bit, so the sender can say 
"this file is for your eyes only."

Jesse