W3C home > Mailing lists > Public > public-sysapps@w3.org > October 2012

Re: Messaging - SMS API draft

From: Kis, Zoltan <zoltan.kis@intel.com>
Date: Fri, 26 Oct 2012 15:55:32 +0300
Message-ID: <CANrNqUdU3yOFbeZrHD50eiysKR1wOs7=1S6A=xj6XrvT8jwKVA@mail.gmail.com>
To: EDUARDO FULLEA CARRERA <efc@tid.es>
Cc: Mounir Lamouri <mounir@lamouri.fr>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Hi Eduardo,

On Fri, Oct 26, 2012 at 3:33 PM, EDUARDO FULLEA CARRERA <efc@tid.es> wrote:
> On 26 oct 2012 at 13:14:35, Kis, Zoltan wrote:
>> MMS is using SMTP on the MM4 interface. So the two specifications
>> (email and MMS) will be almost completely the same, except when you
>> dive into SMIL (which we don't intend to explicitly do in these API's,
>> it will be the middleware's problem).
>>
>
> Though MMS and SMS could live as separate APIs I agree that they can be combined in a single API and probably it is the best solution.
>
> However I strongly disagree that MMS and email are the same case. The interface between the MMS client and the MMS Server is MM1, which is not SMTP but HTTP + WAP Push. MMS cannot be built just making use of an internet connection as it requires the reception of WAP Push notifications and because MNO may require the use of an specific APN for MMS.

I have taken the MM4 interface as an example that MMS can be
transported on SMTP. It is obvious that MMS cannot be *implemented* as
email, the MM1 interface is still there of course :). The point was
they will share mostly the same attributes in a WebIDL interface.

Best regards,
Zoltan
Received on Friday, 26 October 2012 12:56:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 26 October 2012 12:56:02 GMT