Return-Path: Message-ID: Date: Thu, 21 Sep 2006 16:59:40 -0300 From: "Ulisses Furquim" To: "BlueZ development" In-Reply-To: <1158764715.10356.0.camel@localhost> MIME-Version: 1.0 References: <450603BA.3090302@vasmac.com> <1158050613.14015.1.camel@localhost> <45081402.8020909@vasmac.com> <1158313791.5233.9.camel@localhost> <1158764715.10356.0.camel@localhost> Subject: Re: [Bluez-devel] socket connect returns EAGAIN Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net On 9/20/06, Marcel Holtmann wrote: > what about the server socket. In this case EAGAIN is fine. Yes, in this case EAGAIN is fine. However, I don't think we are even calling bt_sock_wait_state() for a server socket (please, correct me if I'm wrong) so changing EAGAIN to EINPROGRESS inside bt_sock_wait_state() should just work, right? (we just need to fix rfcomm_session_create() too and that's it). Regards, -- Ulisses ------------------------------------------------------------------------- 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