Re: Imap Backend Propsal

<campai@cipri.com> wrote : >> There has already have some work done by Wolfram Kriesing on a > Mail_Message >> class for PEAR but it unfortunately does not use the imap extension: >> http://opensource.visionp.biz/120.html >> You might be interested in having a look at that too. >> Personally, I think it is incomplete and relies too much on Net_POP3 and >> sockets at the moment. But the approach is interesting as it could be >> generalized. And I don't like the get/set...() methods, it should use >> overloading to be more flexible. > Using the Net_POP3/socket way about it'd slow it down too much I'm afraid > I've noticed. > >> Apart from that, I am totally pro having a Mail_Message package, as you >> suggested, in PEAR. I can help in testing and fixing bugs but I don't have >> the time to write it from the ground up, so someone has to start >> somewhere... Will it be you, Richard and/or Wolfram ? Can you coordinate >> your efforts ? > As I stated earlier, the code I have right now is totally non OO, totally > integrated into our app already, and way to inefficient to distribute > widely. Since we're already planning on releasing a new version of our app, > the Mail_IMAP package could help a lot there. > >> I was actually thinking about his Mail_Box class. >> Mail_Imap, as it is now, is actually trying to combine both Wolfram's >> Mail_Box and Mail_Message packages. Splitting is probably the way to go. > I'd disagree there. What I could gather about Mail_Box is that it's trying > to provide a wrapper aruond different sorts of sources for mail, be it a POP > / IMAP server, a local file, a directory with mails, etc. Wolfram's > Mail_Message OTOH seems to be used more for reading and generating messages, > which is already provided by other packages (Mail, Mail_Mime, etc). I think > that Richy's Mail_IMAP(For lack of a better name) compliments the Mail and > Mail_MIME packages nicely. COmbine all three, and you have a full fledged > emailing app (Mail to send, Mail_MIME to make, and Mail_IMAP to read > messages). I havn't had the time to try out Mail_IMAP yet, but from what I > saw, all it missed was the ability to pass an already existing IMAP > connection to it. > My request for being able to pass a .eml file to it wouldn't work I just > realized 'cause you couldn't run the imap_*() functions on that. That's true, you'd have to use something like the mailparse extension. So what structure do you guys suggest for that package ? Looks like we will end up with Mail_Imap and that's it ? Personally, I don't have a problem with it. Bertrand Mansion Mamasam