Rich Lafferty ([EMAIL PROTECTED]) said something to this effect on 04/10/2001:
> > I would think that, based on the level of interaction that mutt
> > provides, that a Java applet to interface with mutt would be more
> > appropriate.
>
> At that point, you may as well just use a Java ssh client, and use
> mutt.
>
> I can't at all imagine how you'd do a WWW interface to mutt -- HTTP is
> not character-based. You'd have to send a brand new page every time a
> message arrived in *any* folder (status bar!), and I've no idea how
> you'd send single-character commands without basically rewriting mutt
> in Javascript.
What I would like to see would be a web-based *port* of mutt,
one that would basically use all the same internal functions
other than the mutt_curses stuff (maybe a compatibility layer
between Apache's ap_ functions and the curses stuff?). You could
then use the same .muttrc and it would behave the same way.
Anyone feel ambitious?
(darren)
--
There are trivial truths and there are great Truths. The opposite of a
trival truth is obviously false. The opposite of a great Truth is also true.
-- Neils Bohr
