From: Marcel Holtmann <marcel@holtmann.org>
To: "Fred Schättgen" <bluez-devel@schaettgen.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] More SDP UUIDs...
Date: 17 Sep 2003 01:45:31 +0200 [thread overview]
Message-ID: <1063755937.29942.12.camel@pegasus> (raw)
In-Reply-To: <200309161740.31300.bluez-devel@schaettgen.de>
Hi Fred,
> I'm not sure if this question goes in the same direction, but what happened to
> the idea of a general purpose rfcomm-inetd, which also sets up sdp records
> for its clients? Maybe I'm not really up-to-date, and I didn't find too much
> about it in the archives.. is there one already?
this makes no sense, because the SDP records are application (or call it
profile) specific. And the SDP infos should be coded in the application
itself and not in any master daemon.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-09-16 23:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 22:16 [Bluez-devel] [PATCH] More SDP UUIDs Jean Tourrilhes
2003-09-16 11:33 ` Marcel Holtmann
2003-09-16 13:03 ` David Woodhouse
2003-09-16 15:40 ` Fred Schättgen
2003-09-16 23:45 ` Marcel Holtmann [this message]
2003-09-17 11:34 ` Fred Schättgen
2003-09-19 16:52 ` Marcel Holtmann
2003-09-16 23:49 ` Marcel Holtmann
2003-09-17 6:22 ` David Woodhouse
2003-09-16 19:53 ` Jean Tourrilhes
2003-09-16 23:42 ` Marcel Holtmann
2003-09-17 0:06 ` Jean Tourrilhes
2003-09-17 0:28 ` Marcel Holtmann
2003-09-17 0:36 ` Jean Tourrilhes
2003-09-17 0:58 ` Marcel Holtmann
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=1063755937.29942.12.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.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.