Look, the peak is gone and I’ve cut another two megabytes of ram memory from tinymail. I also improved the load speed (a lot) and the click-speed (snappy feeling). Now Tinymail even works fast when running it under the massif valgrind tool.
Please check it out and try to find problems and issues. Maybe even help me a little bit. I’ve recently posted a todo list (some of the items are already solved) to the mailing list. I’m also looking at implementing a libtinymail-spruce. Nevertheless, this measurement proves that camel can do it. But I still think camel could use some API improvements like simplifying things. Which is why I’m looking at libspruce.
don’t forget to have a look at UW-IMAP and libetpan.
Before implementing a mail client, you should read Javamail design and IMAP literature.
hao: Camel is based on the Javamail design. And as Camel implements (abstracts) most of the dirty IMAP stuff, I try to focus on different aspects of the mail client. Libetpan might be interesting, but for now I’m more interested in libspruce.
But feel free to implement a libtinymail-etpan and/or adjust the interfaces in such a way that it looks more like the Javamail API. Note, however, that most of the Javamail API is very much like both the Camel and libtinymail API.