From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] voicecall: Add EmergencyCall property.
Date: Mon, 06 Dec 2010 20:55:08 -0600 [thread overview]
Message-ID: <4CFDA20C.9020808@gmail.com> (raw)
In-Reply-To: <FE1DB9979BF5A743BEB836613423CAD8012C9C95@fioues07.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
Hi John,
On 12/03/2010 02:00 AM, John.Mathew(a)elektrobit.com wrote:
> Hi Marcel,
>
>>
>>> This was a question open for discussion. What would be the
>> appropriate property name?
>>
>> As per my understanding, this property is only to provide the
>> Emergency call indication to the application side, so that
>> applications can display a different UI compared to the normal
>> UI. In this case, I think the property name "Emergency" is enough.
>>
>> Since this is a property for the call, the following fits as
>> well. We can remove the existing multiparty property and add
>> it to the new property.
>>
>> string Type [readonly]
>> Contains the Type of the current call.
>>
>> The Values can be:
>> "Normal"
>> "Emergency"
>> "Data"
>> "Multiparty"
>>
>> Let me know your opinion on this.
>>
>
> Any comments?
>
We're not going to support data calls, not by re-using the Voicecall
interface anyway. So I still prefer the original proposal of using
boolean Emergency property here.
Regards,
-Denis
next prev parent reply other threads:[~2010-12-07 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 15:12 [PATCH] voicecall: Add EmergencyCall property John Mathew
2010-11-11 15:15 ` Marcel Holtmann
2010-11-11 15:18 ` John.Mathew
2010-11-11 17:01 ` Marcel Holtmann
2010-11-18 11:58 ` John.Mathew
2010-12-03 8:00 ` John.Mathew
2010-12-07 2:55 ` Denis Kenzior [this message]
2010-11-11 15:26 ` Denis Kenzior
2010-11-11 20:22 ` John.Mathew
2010-12-07 12:20 ` [PATCH] voicecall: Add emergency property John Mathew
2010-12-17 17:10 ` Denis Kenzior
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=4CFDA20C.9020808@gmail.com \
--to=denkenz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox