From: Guillaume Zajac <guillaume.zajac@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH] sms: Add delay before submitting multiple SMS to modem
Date: Thu, 23 Aug 2012 16:26:35 +0200 [thread overview]
Message-ID: <50363D9B.80400@linux.intel.com> (raw)
In-Reply-To: <503634B1.90701@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
Hi Denis,
On 23/08/2012 15:48, Denis Kenzior wrote:
> Hi Guillaume,
>
> <snip>
>
>> Unfortunately I come to the conclusion that if I want to send one same
>> SMS to 3/4/5/... recipients with an application using oFono middleware,
>> I will not be able to send them through the same RRC channel, unless I
>> queue them offline.
>>
>
> If such a feature is important, then you do have a point. However,
> implementing _anything_ by introducing an arbitrary delay is simply
> wrong. I believe they teach the reasons for that in Operating Systems
> 101. You are introducing a race condition that will break things at
> the most inopportune time.
I agree that it is not the most elegant/cleanest solution.
>
> If we really require multi-recipient SMS to go on the same RRC
> channel, then the best way to do so would be to introduce a new API
> specifically for this use case.
Having a new API for multi-recipient SMS would be indeed the best solution.
With current implementation the test is passing with multi-segment SMS
using script but GCF test description is mentioning 3 different SMS.
During device certification (with applications), the tester will try to
send an SMS to 3 recipients but it will fail.
Another solution would be to remove multi-SMS support from the PICS.
Kind regards,
Guillaume
next prev parent reply other threads:[~2012-08-23 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 9:29 [PATCH] sms: Add delay before submitting multiple SMS to modem Guillaume Zajac
2012-08-22 22:57 ` Denis Kenzior
2012-08-23 9:04 ` Guillaume Zajac
2012-08-23 13:48 ` Denis Kenzior
2012-08-23 14:26 ` Guillaume Zajac [this message]
2012-08-23 17:33 ` Denis Kenzior
2012-08-24 8:16 ` Guillaume Zajac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50363D9B.80400@linux.intel.com \
--to=guillaume.zajac@linux.intel.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.