Re: Imap Backend Propsal

> >I've written my own webmail client with similar functions in the backend as > >this class proposes, and as such, I'm highly interrested in it. > >As you may or may not know, PHP's imap module can connect to IMAP, POP and > >NNTP via the same functions. Even the data returned will be nearly > >identical. There will be no need at all for a seperate Mail_POP3 class, > >since the Mail_IMAP package will access it just as easily as it would with > >IMAP. That said, I agree with Bertrand about the class name and function > >names. I'd suggest calling it Mail_Message, since it deals with parsing and > >reading of a message. > > Actually my entire package has been created testing on a POP3 account, I don't > have access to an IMAP or NNTP mailbox. As far as what the name of the > package is, I have considered Mail_Cclient but I think since the PHP functions > are called imap_xxxx I'd stick with the Mail_IMAP name, eventhough it is > misleading in that aspect. A verry good point. If the goal of your package is to create an OO wrapper around the C-Client code, then Mail_IMAP is a fitting name, I must agree. But like I said earlier, not every ability will be guaranteed to work so in this case you should give some thought about that. If its goal is to provide an easy interface towards Finding and Fetching data about a mail-message, then perhaps a name along the lines of Mail_Message(Fetch) could prove to be more usefull.