Re: PEAR on Win32

Quoting Sterling Hughes <sterling@designmultimedia.com>: > > > Mail/SMTP > > > > I'd actually like to break this one out into a seperate hierarchy: > > > > Mailer/SMTP > > Mailer/Sendmail > > Mailer/PHP > > > > I don't know about this, I think that SMTP clearly fits into the Mail > catagory. So does Mail/Sendmail Okay... maybe then: Mail/Mailer Mail/Mailer/SMTP Mail/Mailer/Sendmail etc... It's a bit more typing, but I want a common interface between the classes that send mail - if Mail/ also contains Mail/POP, then it isn't the place for that API, but it should exist, which is why I'm suggesting Mailer/ or Mail/Mailer. > Why not just keep it all in Mail? No reason - just typing. But it does fit there. > Perhaps we should have a message subclass: > > Message/HTML > Message/MIME > Message/* Urg. An HTML email _is_ a MIME email. Just a specialized kind of one. That should be strangled. Err, did I say that? And back at you: why should Message/ be outside of Mail/? Too many inter-related not-quite-standards... > as well as a MIME sub-folder for non-message related topics. > > This could get a bit complicated, but I think MIME/application/msword and > MIME/Message shouldn't be in the same sub-class (you had to put msword in > there:-). Yeah... Hmm. Maybe MIME/application/msword is a bit specific to have in PEAR - maybe we should provide a MIME/viewer interface that applications can implement to handle various types... -chuck -- Charles Hagenbuch, <chuck@horde.org> -- "we are plastered to the windshield of the bus that is time." - Chris