[Bug 24907] SMS extensions for Messages

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=24907

Will Thompson <will.thompson at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://git.collabora.co.uk/
                   |                            |?p=user/wjt/telepathy-spec-
                   |                            |wjt.git;a=shortlog;h=refs/h
                   |                            |eads/chan-iface-sms
           Keywords|                            |patch

--- Comment #3 from Will Thompson <will.thompson at collabora.co.uk> 2010-08-13 02:44:44 PDT ---
(In reply to comment #2)
>  - SMSServiceCentre
> Either Cellular/SMS-specific, or part of ServicePoint
> (Service_Point_Type_Unknown or add a new type).

Decided that there's no need for this to be per-channel. It's already on
Cellular, and if we need a way to override this in the future, it should be a
message header. Binned.

>  - SMSValidityPeriod
> SMS-specific, for both Connections and Channels.  Made part of Cellular.

Indeed. Binned.

>  - Flash
> Required for regulatory reasons.  Boolean, and only necessary for a channel
> interface.  Not necessarily cell/SMS specific; could be thought of as an
> Emergency or Urgency-style property, and made part of Text (as a channel
> property) or ServicePoint as a point type (either adding a new SP type, or as
> Service_Point_Type_Emergency).

Here's a Channel.Interface.SMS with a single Flash boolean property:
<http://people.freedesktop.org/~wjt/telepathy-spec-chan_iface_sms/spec/Channel_Interface_SMS.html>.
While this is not necessarily cellular-specific, currently SMS is the only
implemented protocol with this regulatory requirement, and having a single
boolean makes writing the HandlerChannelFilter very straightforward.

>  - TargetMatch
> This is not something that should be exposed to the client; it's the CM's job
> to figure out how to match channels based upon the protocol.  Also, as Rob
> pointed out, this is not just a problem w/ GSM; it's also an issue w/ SIP as
> well.  As such, it's beyond the scope of this bug.  Dropped.

As it turns out, this property was not actually used in Maemo 5. The length of
the string to match is region-specific, and matching is much easier if you have
access to the user's full address book. (For instance, if you have a conflict,
the UI could consider further characters until the conflict is resolved.)

So, dropped, and left up to the UI.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.