From owner-freebsd-bluetooth@FreeBSD.ORG Wed May 21 00:02:46 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4EAF1065670 for ; Wed, 21 May 2008 00:02:46 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 20EBB8FC14 for ; Wed, 21 May 2008 00:02:45 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-148-169.lns11.adl6.internode.on.net [121.45.148.169]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m4L02grl098234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 21 May 2008 09:32:43 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Maksim Yevmenkin" Date: Wed, 21 May 2008 09:32:39 +0930 User-Agent: KMail/1.9.7 References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805200845.57007.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1255834.XBC80CXTYJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200805210932.40993.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2008 00:02:47 -0000 --nextPart1255834.XBC80CXTYJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 20 May 2008, Maksim Yevmenkin wrote: > > Why would you be multiplexing it? It's a virtual serial port, pty > > sounds like a pretty good match. ie I think I am misunderstanding > > what you are trying to say. > > ok, i will give you an example. lets say i have a couple of bluetooth > devices. lets say device #1 is a handheld and device #2 is some other > client device that wants to use serial port service on the pc. say, > its a bluetooth scanner/keyboard/etc. type device that proactively > connects to the host computer and sends stream of data. > > with virtual serial port there is no real need to register two (or > more) serial port services on the host pc. one could argue that > rfcomm_sppd(1) should have a configuration file that says > > if connected to device #1 { execute sync application } > if connected to device #2 { dump data } > > technically, both devices could use the same serial port service > registered on the same rfcomm channel on the same host pc. the data > coming from two different rfcomm connections from two different > devices. the server bluetooth endpoint just happens to be the same, > but the server will have two connections and two separate pty's for > both clients. this is the soft of multiplexing i'm talking about. the > same will work in client mode too. OK. > > Mmm good point :( > > I was thinking that in server mode it opened the PTY then waited > > for a connection but that isn't the case.. > > this is the case. it opens pty first then it does listen/accept/etc. Huh yes so it does! > > I am not sure how/why server mode is actually used - I only have > > experience with devices that are basically using BT as an RS232 > > replacement. > > right, there aren't many examples of server mode usage, but i was > thinking about "serial console" over bluetooth type thing. of course > it will never be a real serial console, just another out-of-band > access. could be useful to somebody. Selfishly, I think it's better to focus on the client stuff - heck I use=20 it, so must everyone else ;) I wonder if the server stuff should be split into a separate program. At=20 the moment rfcomm_sppd works perfectly well as a client program (with=20 my patch anyway ;) but server mode needs more work to be properly=20 useful (IMO) as it needs the config file and ability to exec stuff on=20 demand etc.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1255834.XBC80CXTYJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIM2ag5ZPcIHs/zowRAjJoAJwMupdVBzQ2aq43rzZEdqUDVH15HgCeIOWq yiIatMtl7HsSj4zIa5l8RyA= =tZgq -----END PGP SIGNATURE----- --nextPart1255834.XBC80CXTYJ--