From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: RE: [Bluez-devel] RFCOMM communication gets stalled From: Marcel Holtmann To: "Williams, Richard" Cc: "Bluez-Devel (E-mail)" In-Reply-To: References: Content-Type: text/plain Message-Id: <1089915789.4517.43.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 15 Jul 2004 20:23:09 +0200 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