2 Apr
2003
2 Apr
'03
11:08 p.m.
Alexandre, I replay this mail e-mail to the
mailing-lists as others are
probably also interested in those questions.
Hummm
If I try to get into an end-user shoes, I think the idea of adding manually a mime type is
not so friendly.
Why not to infer it by regarding the file extension?
I do not really like to be obliged to type the string image/jpeg when I want to upload an
image.
Something else, why not to hide all the resource structure?
When I add an image from the link *my supper great image*, I am not so interested by
having an entry named 'my supper great image' in the folder...
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I would like to play with resource, but I am stop
by some issues:
- What Mimetype means?
The mime-type describes the type of a file in a platform independent
manner. The browser needs this information to know how to display the
resource.
If you like to know more about the internals of the http-protocol I
suggest to read the standard-documentation. There you will find also
references to documents about the mime-type standard:
Hypertext Transfer Protocol -- HTTP/1.1
http://www.ietf.org/rfc/rfc2616.txt