In <iluelwesbyt(_dot_)fsf(_at_)barbar(_dot_)josefsson(_dot_)org> Simon
Josefsson <simon(_at_)josefsson(_dot_)org> writes:
Another idea to throw into this thread would be RFC 2387 on the
text/x-okie MIME type, which seem to be a solution to this problem.
It's only used as an example in the RFC, and I do not know if anything
became of the text/x-okie idea, but it shows that others has
considered this to be a problem worth solving before.
OK, but it does introduce a worry that people are defining all sorts of
very specialized Mime extensions for perceived applications, without
looking for more generalized extensions that will cover a whole class of
applications, which implementors of browsers would be more likely to
And how is it that an official RFC has managed to define a token staring
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk Snail: 5
Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5