Do you think that following unknown content types are suitable:
http - frame content: text/html
http - image: image/gif
local file DOS: binary
local file Linux: text/plain
ftp file: binary
e-mail attchment: binary
One of important things to do is linking e-mail attachments using "cid:"
protocol, instad of "file:". This will increase security, and it would
allow correct processing of e-mail MIME types and filenames - becasu
stupid Window mailers often assigne incorrect MIME type for given
extension, so Arachne now either uses incorrect filename, or incorrect
MIME type. So HTML pages are attached as text/plain, which prevents them
from being viewed propely in Arachne. This could be solved by caching
attachments as objects with URL cid:content-id, with MIME type defined by
something else than extension... well, this wont help with text/plain for
HTML, thats problem... :-(
It would be also possible to add better support for multipart/alternative
MIME e-mail messages, to show HTML version of message in specialy
generated TABLE tag, which would allow for special graphical effects.
Also, Arachne mailto: screen can be updated to allow editation of outgoing
MIME type... allowing users to compose outgoing messages as HTML pages is
up to me, but any programmer is invited to modify open-sourced InSight to
view alternative HTML content correctly....
--
http://arachne.cz/
(Arachne WWW browser for DOS+Linux / Webhosting / MP3streaming)
