public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [Bluez-users] PANU service search
Date: Mon, 28 Mar 2005 11:07:13 -0300	[thread overview]
Message-ID: <e1effdeb0503280607600d1863@mail.gmail.com> (raw)
In-Reply-To: <1112016560.9016.32.camel@pegasus>

Hi Marcel,

Suppose an UPnP application where a control point(role GN controller)
needs search for
services in several servers. The control point is the active member
and it will search for other devices. It must be the GN controller
because sometimes foward packet is required.

The UPnP search takes few seconds therefore connect and search for UPnP service
on each server is unacceptable.

Someone can suggest use a search for UPnP service at bluetooth SDP level,
searching only devices that provide UPnP service. It solve the problem
for ad hoc
networks, but can't solve in network access point scenario. This is the reason 
for establish the PAN and after use the UPnP search.

Regards,
Claudio.



On Mon, 28 Mar 2005 15:29:20 +0200, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
> 
> > The sdptool doesn't provide search for PANU service. Is there plans
> > for implement this?
> 
> you can do it by "sdptool search --bdaddr <bdaddr> 0x1115".
> 
> > A PANU device can be started with the following command:
> > pand --listen --role PANU
> >
> > This scenario can be usefull when there are a lot of servers and a
> > client device works as a GN connecting these servers. eg: UPnP applications.
> 
> The pand client can search for PANU by itself and I don't see any real
> use for it. However send in a patch for it.
> 
> Regards
> 
> Marcel
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-03-28 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 13:22 [Bluez-users] PANU service search Claudio Takahasi
2005-03-28 13:29 ` [Bluez-devel] " Marcel Holtmann
2005-03-28 14:07   ` Claudio Takahasi [this message]
2005-03-28 14:18     ` Marcel Holtmann
2005-03-28 19:03       ` Claudio Takahasi
2005-03-28 19:22         ` Marcel Holtmann
2005-03-28 19:46           ` Claudio Takahasi
2005-03-28 20:01             ` Marcel Holtmann
2005-03-28 20:48               ` Claudio Takahasi

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=e1effdeb0503280607600d1863@mail.gmail.com \
    --to=cktakahasi@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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