|
Posted by Slaven Rezic on August 15, 2005, 10:24 pm
Please log in for more thread options
> Further thought on the namespace has yielded these suggestions:
>
> MMS::MailMessage::Parsed - A class representing an MMS parsed from an
> email
> MMS::MailMessage::ProviderParsed - A class represnting an MMS that has
> had provider information/spam/advertising removed
> MMS::MailParser - The main parsing class
> MMS::ProviderMailParser::$SOMEPROVIDER$ - A static class containing the
> decoding rules for a particular network provider (e.g. Vodafone UK
> encode their messages with HTML)
>
> This leaves space for the creation of an MMS::Message class
> implementing the binary spec found at
>
http://www.openmobilealliance.org/tech/affiliates/LicenseAgreement.asp?DocName=/wap/wap-209-mmsencapsulation-20020105-a.pdf
> and also for creation of an MMS Server class.
>
> Anybody have any thoughts/objections ?
>
Much better. I also wanted to point to the binary (or XML based) MMS
specifications.
What is the exact value of $SOMEPROVIDER? Is the country coded in,
e.g. Vodafone_UK?
Regards,
Slaven
--
Slaven Rezic - slaven <at> rezic <dot> de
Tired of using file selectors? Real programmers use the TAB key for
completion and not for jumping around. Try
http://search.cpan.org/search?mode=module&query=Tk::PathEntry
|