linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gowtham Anandha Babu <gowtham.ab@samsung.com>
To: 'Luiz Augusto von Dentz' <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org,
	'Dmitry Kasatkin' <d.kasatkin@samsung.com>,
	'Bharat Panda' <bharat.panda@samsung.com>,
	cpgs@samsung.com
Subject: RE: [PATCH 5/6] obexd/messages: Add prototypes for MASInstance response
Date: Wed, 08 Oct 2014 19:22:28 +0530	[thread overview]
Message-ID: <001a01cfe2ff$28eef300$7accd900$@samsung.com> (raw)
In-Reply-To: <CABBYNZ+-AepnfRqmKxUhtTdfF_9-b0+mQfdNkLB+HBLhZe=c5Q@mail.gmail.com>

Hi,

> -----Original Message-----
> From: Luiz Augusto von Dentz [mailto:luiz.dentz@gmail.com]
> Sent: Wednesday, October 08, 2014 6:01 PM
> To: Gowtham Anandha Babu
> Cc: linux-bluetooth@vger.kernel.org; Dmitry Kasatkin; Bharat Panda;
> cpgs@samsung.com
> Subject: Re: [PATCH 5/6] obexd/messages: Add prototypes for MASInstance
> response
> 
> Hi,
> 
> On Wed, Oct 8, 2014 at 3:09 PM, Gowtham Anandha Babu
> <gowtham.ab@samsung.com> wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: Luiz Augusto von Dentz [mailto:luiz.dentz@gmail.com]
> >> Sent: Wednesday, October 08, 2014 4:42 PM
> >> To: Gowtham Anandha Babu
> >> Cc: linux-bluetooth@vger.kernel.org; Dmitry Kasatkin; Bharat Panda;
> >> cpgs@samsung.com
> >> Subject: Re: [PATCH 5/6] obexd/messages: Add prototypes for
> >> MASInstance response
> >>
> >> Hi,
> >>
> >> On Tue, Oct 7, 2014 at 7:06 AM, Gowtham Anandha Babu
> >> <gowtham.ab@samsung.com> wrote:
> >> > ---
> >> >  obexd/plugins/messages.h | 16 ++++++++++++++++
> >> >  1 file changed, 16 insertions(+)
> >> >
> >> > diff --git a/obexd/plugins/messages.h b/obexd/plugins/messages.h
> >> > index
> >> > 00a16b1..3aaeec1 100644
> >> > --- a/obexd/plugins/messages.h
> >> > +++ b/obexd/plugins/messages.h
> >> > @@ -307,3 +307,19 @@ int messages_set_delete(void *session, const
> >> > char
> >> *handle, uint8_t value,
> >> >   * session: Backend session.
> >> >   */
> >> >  void messages_abort(void *session);
> >> > +
> >> > +
> >> > +
> >> > +/* Retrieves MAS Instance Information for the given mas-instance id.
> >> > + *
> >> > + * session: Backend session.
> >> > + * mas_id: MAS Instance id requested by the MCE.
> >> > + *
> >> > + * Callback shall be called for every mas_instance_id request
> >> > +received
> >> from MCE.
> >> > + */
> >> > +typedef void (*messages_mas_instance_info_cb)(void *session, int
> err,
> >> > +               uint16_t size, const char *name, void *user_data);
> >> > +
> >> > +int messages_get_mas_instance_info(void *session, uint16_t
> >> mas_instance_id,
> >> > +                               messages_mas_instance_info_cb callback,
> >> > +                               void *user_data);
> >> > --
> >> > 1.9.1
> >>
> >> You can drop using mas here since it is pretty obvious what it is
> >> for, also Im not sure we need the size in the callback since we can use
> strlen there.
> >>
> >>
> >> --
> >> Luiz Augusto von Dentz
> >
> > I agree with you. I will update this comment for the patch[6/6] too. I will
> include this in v2. Still is there anything to be handled?
> 
> Start with the server side, I will be working on the client side to add support
> for multiple instances, I have something already it just need some polishing.
> 
> --
> Luiz Augusto von Dentz

I think not much implementation in server side is needed. 
No features are using the instance id in server side except this patch set. But can be added as below:

1)Define no_of_mas_instance (assign no of instances if it supports or '0')
2)While MCE discovering for MAS service, advertise all mas id's(if it supports more than one)
3) While mas_connect(), need to look match for which mas_id the MCE requesting
4) Folder ordering for multiple MAS instance is needed as you suggested. Like
MAS 1/telecom/...
MAS 2/telecom/...

Once the client part is known, we can implement that accordingly. 

Meanwhile is this patch set good to go?

Regards,
Gowtham Anandha Babu


  reply	other threads:[~2014-10-08 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07  4:06 [PATCH 0/6] Add support for MAP MASInstance feature Gowtham Anandha Babu
2014-10-07  4:06 ` [PATCH 1/6] doc/obex-api: Add description about MASInstance request Gowtham Anandha Babu
2014-10-07  4:06 ` [PATCH 2/6] test/map-client: Add D-Bus API support to make " Gowtham Anandha Babu
2014-10-07  4:06 ` [PATCH 3/6] obexd/client/map: Add API Calls for request and handlers for response Gowtham Anandha Babu
2014-10-07  4:06 ` [PATCH 4/6] obexd/mas: Add support for providing MASInstance Info as response Gowtham Anandha Babu
2014-10-07  4:06 ` [PATCH 5/6] obexd/messages: Add prototypes for MASInstance response Gowtham Anandha Babu
2014-10-08 11:12   ` Luiz Augusto von Dentz
2014-10-08 12:09     ` Gowtham Anandha Babu
2014-10-08 12:31       ` Luiz Augusto von Dentz
2014-10-08 13:52         ` Gowtham Anandha Babu [this message]
2014-10-07  4:06 ` [PATCH 6/6] obexd/message-dummy: Add MAS Instance description to response Gowtham Anandha Babu
2014-10-08 10:38 ` [PATCH 0/6] Add support for MAP MASInstance feature Luiz Augusto von Dentz
2014-10-08 12:08   ` Gowtham Anandha Babu

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='001a01cfe2ff$28eef300$7accd900$@samsung.com' \
    --to=gowtham.ab@samsung.com \
    --cc=bharat.panda@samsung.com \
    --cc=cpgs@samsung.com \
    --cc=d.kasatkin@samsung.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).