It is my understanding that the biggest issue with IMAP web interfaces is connection handling. Basically there is no connection pool for IMAP on most, at least PHP, web clients.
This can be handled easily by implementing something like Perdition IMAP Proxy that has its own connection handling, in addition to other great scalability features, that will help significantly with this IMAP *Client* issue. As pointed out by Mike, I'm pretty sure it is not a protocol or server issue... it is really a client connection handling issue. Kevin > What utter nonesense blaming the protocol for bad front > -end code. Fix your > code. > > Mike > > > > > > ----- Original Message ----- > From: "Igor Stroh" <[EMAIL PROTECTED]> > To: "DBMAIL Developers Mailinglist" > <dbmail-dev@dbmail.org> > Sent: Monday, August 01, 2005 5:18 AM > Subject: Re: [Dbmail-dev] dbmail web interface > > >> Paul J Stevens wrote: >>> Brandon, >>> >>> why reinvent the wheel here? Either use imap where >>> access is restricted >>> to your client, or build a client that links directly >>> to libdbmail. >>> >>> Please take not that 2.1 development is under way, and >>> the tables will >>> change a bit here and there as we add new features or >>> improve >>> performance. Imap is very much the interface of choice >>> until we manage >>> to make libdbmail a truly shareable library, and >>> provide cross language >>> interfaces to the data storage. >> >> FWIW, IMAP sucks badly when it's used as a backend for >> large scaled >> webmailers, I chose DBMail because it offers the >> possibility to access >> mailboxes directly through SQL... >> >> [...] >> >> Just my two cents :) >> >> Cheers, >> Igor >> _______________________________________________ >> Dbmail-dev mailing list >> Dbmail-dev@dbmail.org >> http://twister.fastxs.net/mailman/listinfo/dbmail-dev >> > > _______________________________________________ > Dbmail-dev mailing list > Dbmail-dev@dbmail.org > http://twister.fastxs.net/mailman/listinfo/dbmail-dev >
