Huh? What changes? Today I expect the mail user agent to invoke the
receiving agent which, after it does its stuff, invokes the browser.
In the future the receiving agent functionality gets incorporated into
combined or cooperative mail agents and Web browsers.
Today, the browser gets what it sees now; no change!
No change to the mail user agent beyond support for Multipart/Related.
That change or new requirement we agree on, don't we?
So there must be something unclear since you prefer a solution that
uses existing Web browsers and I'm suggesting a model that does just
that.
There is no single receiving agent, rather one is needed that matches
the storage and cache capabilities of a mail agent and browser pair.
I don't think we'll need a lot of those and perhaps the receiving
agent functionality could be configurable.
Ed
On Tue, 07 Nov 1995 10:45:42 +0100 Jacob Palme wrote:
...
The problem with your idea is that it requires changes in the coding
of all existing Web browsers. This will take a long time to get
implemented. I would much prefer a solution where most existing
Web browsers can be used as they are.