From: Marcel Holtmann <marcel@holtmann.org>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>
Cc: "Bluez-Devel (E-mail)" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] RFCOMM communication gets stalled
Date: Thu, 15 Jul 2004 20:23:09 +0200 [thread overview]
Message-ID: <1089915789.4517.43.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A45BDC76@goofy.vitronics.com>
Hi Richard,
> I use the rfcomm tty interface quite successfully for sending GPS data
> strings from a GPS receiver to an Ipaq and then to another small wrist display.
> Why use the rfcomm socket interface instead of the TTY ?
>
> Should I consider changing my code from TTY to socket ? Its not so difficult, I just
> wonder why you recommend one vs the other.
the question is what is the advantage of keeping a legacy TTY if you
already have the source code? There is no difference between a socket
descriptor and a file descriptor, so why involve another subsystem?
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
next prev parent reply other threads:[~2004-07-15 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 18:11 [Bluez-devel] RFCOMM communication gets stalled Williams, Richard
2004-07-15 18:23 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-15 14:21 Carlos AM
2004-07-15 17:48 ` 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=1089915789.4517.43.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Richard.Williams@VITRONICS.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