linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suraj Sumangala <suraj@Atheros.com>
To: "Waldemar.Rymarkiewicz@tieto.com" <Waldemar.Rymarkiewicz@tieto.com>
Cc: Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>,
	"joakim.xj.ceder@stericsson.com" <joakim.xj.ceder@stericsson.com>,
	"claudio.takahasi@gmail.com" <claudio.takahasi@gmail.com>,
	"Arkadiusz.Lichwa@tieto.com" <Arkadiusz.Lichwa@tieto.com>
Subject: Re: [RFC] Sim Access Profile API doc
Date: Tue, 7 Sep 2010 14:58:04 +0530	[thread overview]
Message-ID: <4C8605A4.3020300@Atheros.com> (raw)
In-Reply-To: <99B09243E1A5DA4898CDD8B7001114480979581239@EXMB04.eu.tieto.com>

Hi Waldek,

On 9/7/2010 2:06 PM, Waldemar.Rymarkiewicz@tieto.com wrote:
> Hi Suraj,
>
>> From: Suraj Sumangala [mailto:suraj@atheros.com]
>> Sent: Tuesday, September 07, 2010 8:03 AM
>
>> +
>> +		void Disconnect(string type)
>> +
>> +			This initiates a SAP disconnection from
>> SAP server.
>> +
>> +			The type parameter specifies the type
>> of disconnection.
>> +
>> +			"Graceful"  ->  lets the SAP client initiate a
>> +			garceful disconnection.
>> +
>> +			"Immediate" ->  disconnects the connection
>> +			immediately from the server.
>> +
>
> In my view, the disconnection should be initiates by the sap server, not by the agent. In a typical use case the agent will communicate sim state change (card removed or not accessible) to sap server. Based on that, the sap server should make a decision whether disconnect or not. What's more the disconnect procedure is defined in the SAP spec, and would be nice to keep all those procedures in the sap server, not in the agent which will be specific for a sim provider.  Therefore, I would remove this method call from the api.  I would add the Disconnect signal instead.
>
> Signal:
> Disconnect()
>        This signal will be send when SAP connectionis successfully removed.
>
> In case of graceful  disconnection sap server sends signal to the agent REQUEST(disconnect) and wait till  SIM free its stuff and send back RESPONSE(disconnect). In case  of immediate disconnection sap server will send Disconnect() signal to the agent.

Ok, In which all situations should the SAP server decide that the SAP 
connection has to be disconnected (you have mentioned Sim Status change 
as one candidate)?

Also, based on what should the server decide to initiate a "Graceful" or 
"Immediate" disconnection?

>
> Thanks,
> /Waldek

Regards
Suraj


  reply	other threads:[~2010-09-07  9:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  6:02 [RFC] Sim Access Profile API doc Suraj Sumangala
2010-09-07  7:47 ` Uwe Kleine-König
2010-09-07  8:36 ` Waldemar.Rymarkiewicz
2010-09-07  9:28   ` Suraj Sumangala [this message]
2010-09-07 12:24     ` Waldemar.Rymarkiewicz
2010-09-07  9:29 ` Johan Hedberg
2010-09-07  9:58   ` Suraj Sumangala
2010-09-07 10:12     ` Johan Hedberg
2010-09-07 12:54       ` Suraj Sumangala

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=4C8605A4.3020300@Atheros.com \
    --to=suraj@atheros.com \
    --cc=Arkadiusz.Lichwa@tieto.com \
    --cc=Jothikumar.Mothilal@Atheros.com \
    --cc=Suraj.Sumangala@Atheros.com \
    --cc=Waldemar.Rymarkiewicz@tieto.com \
    --cc=claudio.takahasi@gmail.com \
    --cc=joakim.xj.ceder@stericsson.com \
    --cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).