From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO on bluez : some architectural tips
Date: Sat, 18 Nov 2006 11:02:11 +0100 [thread overview]
Message-ID: <455EDA23.5020003@free.fr> (raw)
In-Reply-To: <ef9938ec0611161238p63da651dr497c04024c8ecbb7@mail.gmail.com>
Hi Albert,
>> * The unix socket between application and the daemon would queue some
>> data, which would add unwanted delay.
>
> just curious, was setvbuf( fp, NULL, _IONBUF, 0 ) to disable socket
> buffering an option?
>
In our case we use direct read/write calls from socket descriptor, which
means that setvbuf is useless, as it works at libc layer.
Good try anyway ;-)
Cheers,
Fabien
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-18 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 20:32 [Bluez-devel] SCO on bluez : some architectural tips Fabien Chevalier
2006-11-16 20:38 ` Albert Huang
2006-11-17 6:46 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:02 ` Fabien Chevalier [this message]
2006-11-16 21:56 ` [Bluez-devel] " Brad Midgley
2006-11-18 10:07 ` Fabien Chevalier
2006-11-19 5:45 ` Brad Midgley
2006-11-19 17:02 ` Fabien Chevalier
2006-11-17 6:45 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:27 ` Fabien Chevalier
2006-11-18 11:44 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-19 5:30 ` Brad Midgley
2006-11-19 16:54 ` Fabien Chevalier
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=455EDA23.5020003@free.fr \
--to=fabchevalier@free.fr \
--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