> So, If I create a 3D-program, I could say that file extensions for this
> program will be .pdf (not a prefered extension, but still)?
> Is it more a question of getting your file extension as widely used as
> possible, so other companies dont bother using them, since most computers
> have them associated with an other program?
Basically, what he's saying is that the extension can be anything. It's
only convention (and only on pc/unix) where it's important to determine
what kind of file it is. On advanced filesystems, such as HFS+(mac),
beFS(beos), and such the type of file is kept as an extended attribute
and you can call your jpeg image myimage.doc and it will still get
sent to the correct application when you double click on it. I think ntfs
and hpfs have the ability to do this, but it's not implemented.
Mime types are things like tex/html and image/jpeg that describe what
kind of file you're dealing with. They are what beFS uses to keep track
of what's in a file.
The reason for extensions is that in unix/windows/dos, all files are the
same, they have no type, they're all just a string of bytes, and the
original inventors or unix needed a way to tell one file from another.
Gfunk - http://www.gfunk007.com/
I sense much beer in you. Beer leads to intoxication, intoxication to
hangovers, and hangovers to... suffering.
>
> > MIME-types do what you need. But they don't belong to the filename.
>
> What do you mean by this?
>
> Regards,
> // Tobias
>
>
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
