All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <survivor@uni-paderborn.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP service example
Date: Fri, 16 Jul 2004 08:38:26 +0200	[thread overview]
Message-ID: <1089959906.4517.55.camel@pegasus> (raw)
In-Reply-To: <40F70E09.7010300@uni-paderborn.de>

Hi Stefan,

> I'm looking for a small example to show me how to write my own SDP 
> service? Particularly, I'd like to know where exactly the service 
> functions of my new service are bound to SDP. I looked into the souce 
> code, but I couldn't find it. I almost suppose SDP just provides the 
> L2CAP channel id where the new service is listening or how does it work? 
> Sorry, I'm not so much into this Linux developer thing and I have not 
> yet found any good documentation. I'm also looking for docs how this 
> Linux/Unix socket interface stuff works (preferably in German ;-). Yes, 
> I checked the manpages, but they are not quite explanatory.

look at the source code of pand, dund or sdptool.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2004-07-16  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15 23:06 [Bluez-devel] SDP service example Stefan Mischke
2004-07-16  6:37 ` Collin R. Mulliner
2004-07-16  6:38 ` Marcel Holtmann [this message]

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=1089959906.4517.55.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=survivor@uni-paderborn.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.