Linux bluetooth development
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Mikel Astiz <mikel.astiz@bmw-carit.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC obexd 05/10] client-doc: replace parameter dict with conventional ones
Date: Thu, 24 Nov 2011 15:24:57 -0300	[thread overview]
Message-ID: <20111124182457.GB20733@samus> (raw)
In-Reply-To: <1322143742-31182-6-git-send-email-mikel.astiz@bmw-carit.de>

Hi Mikel,

On 15:08 Thu 24 Nov, Mikel Astiz wrote:
> The usage of a dictionary as a parameter passing mechanism seems not to
> be necessary any more.
> ---
>  doc/client-api.txt |   22 ++++++++++------------
>  1 files changed, 10 insertions(+), 12 deletions(-)
> 
> diff --git a/doc/client-api.txt b/doc/client-api.txt
> index a6f30af..67355c6 100644
> --- a/doc/client-api.txt
> +++ b/doc/client-api.txt
> @@ -12,27 +12,25 @@ Service		org.openobex.client
>  Interface	org.openobex.Client
>  Object path	/
>  
> -Methods		object CreateSession(dict device)
> +Methods		object CreateSession(string source, string destination,
> +					string target)
>  
> -			Create a new OBEX session. The device is configured
> -			via properties like in SendFiles.
> +			Create a new OBEX session for the given source (local)
> +			address, destination (remote) address and target. The
> +			supported target values are:
> +				- "OPP"
> +				- "FTP"
> +				- "SYNC"
> +				- "PBAP"
>  
>  		void RemoveSession(object session)
>  
>  			Unregister session and abort pending transfers.
>  
> -		string GetCapabilities(dict device)
> +		string GetCapabilities(string source, string destination)
>  
>  			Get remote device capabilities.
>  
> -Properties	string Target
> -
> -		string Source
> -
> -		string Destination
> -
> -		byte Channel

I just wanted to say that for most of the cases doing the SDP seach 
always is the right thing to do, but sometimes you want to avoid it.

I agree that for now we can leave it, but it would be nice if there
was a way to add it later if we ever need it.

> -
>  Session hierarchy
>  =================
>  
> -- 
> 1.7.6.4
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Cheers,
-- 
Vinicius

  reply	other threads:[~2011-11-24 18:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 14:08 [RFC obexd 00/10] Major API changes in obex-client Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 01/10] client-doc: reformatted to fit in 80 columns Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 02/10] client-doc: copyright statement added Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 03/10] client-doc: minor formatting changes Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 04/10] client-doc: wrap OPP into specific session type Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 05/10] client-doc: replace parameter dict with conventional ones Mikel Astiz
2011-11-24 18:24   ` Vinicius Costa Gomes [this message]
2011-11-25 11:52     ` Luiz Augusto von Dentz
2011-11-25 13:41       ` Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 06/10] client-doc: remove agent in favour of transfer signals Mikel Astiz
2011-11-25 12:01   ` Luiz Augusto von Dentz
2011-11-24 14:08 ` [RFC obexd 07/10] client-doc: ObjectPush sessions return transports Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 08/10] client-doc: FileTransfer " Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 09/10] client-doc: PhonebookAccess " Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 10/10] client-doc: Synchronization " Mikel Astiz
2011-11-24 18:11 ` [RFC obexd 00/10] Major API changes in obex-client Vinicius Costa Gomes
2012-01-13 14:24 ` Luiz Augusto von Dentz
2012-01-13 15:53   ` Mikel Astiz

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=20111124182457.GB20733@samus \
    --to=vinicius.gomes@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mikel.astiz@bmw-carit.de \
    /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