I was thinking along the lines of Shantonu Sen <[EMAIL PROTECTED]> (nmh as 
client) where we take advantage of nmh's powerful command line 
interface and give the core of nmh the ablilty to work on other media 
than raw (nmh) files. It should be possible to define a suitable 
abstraction of a mail in an OO-ish way and implement "plugins" for the 
various storage formats (nmh, imap, etc).

The trick is (which this thread already has discovered) to model stuff 
like sessions/contexts and to make the environment configurable for 
user while keeping .mh_profile sane and not overly bloated with stuff 
from various storage fromats.


As a comment to the caching issue discussed in the thread I'd like to 
see that handled _inside_ the "object" which handles imap storages.

/Anders


Disclaimer, "Object" does not mean C++, you can do OO-like design in C. 
   


> > Anders Eriksson:
> 
> > Are you thinking of an nmh backend to an imap server or nmh ans an imap 
> > client? I'd love to see the actual storage used in nmh 'virtualized', 
> > so we can have the same powerful command line interface and different 
> > storages (mh files, mbx, mbox, imap, ...)
> 
> please elaborate on this.
> 
> clemens
> 


PGP signature

Reply via email to