Re: Hydrant C++

[Alain Magloire]

> on  one vision of what is a mailbox and how to access it.  So
> the object "mailbox_t" and the object "message_t" are just empty
> or virtual class (in our case pointers to functions in a structure) that
> the different format implements, So the POP will implement the
> int (*read)() function of message_t differenty then the int *(read)()
> function of IMAP.  In the former case a "RETR %d\r\n" is generate and the
> later a "tag FETCH % BODY[]\r\n" is send.

Should have pointed that a mailbox_t/message_t do not have to be EMAILs
for example we could have a slashdot mailboxes.

{
        mailbox_create (&mbox, "slashdot://www.slashot.org");
....
}

or the messages maybe sitting on an SQL databases;

{
        mailbox_create (&mbox, "sql://database.com");
....
}

or maybe the emails or only accessibe via hotmail but you don't
like the web interface and rather use hydrant funky layout.

{
        mailbox_create (&mbox, "hotmail://address@hidden");
....
}

Once the backend is implemented suddenly those little programs
take a new meaning.

# MAIL=slashot://www.slashdot.org ./from

For example, for Elm to take advantage of this will require some
serious code change. Pine OTO can get away with it since it uses
the c-client as the backend.  Mutt I do not know.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!