From owner-freebsd-bluetooth@FreeBSD.ORG Tue Oct 26 08:19:33 2010 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 4532B1065694 for ; Tue, 26 Oct 2010 08:19:33 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp6.freeserve.com (smtp7.freeserve.com [80.12.242.2]) by mx1.freebsd.org (Postfix) with ESMTP id CD1658FC0C for ; Tue, 26 Oct 2010 08:19:32 +0000 (UTC) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3j02.me.freeserve.com (SMTP Server) with ESMTP id 2FED6300008B; Tue, 26 Oct 2010 10:19:31 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3j02.me.freeserve.com (SMTP Server) with ESMTP id 223773000095; Tue, 26 Oct 2010 10:19:31 +0200 (CEST) Received: from rya-online.net (unknown [89.194.99.220]) by mwinf3j02.me.freeserve.com (SMTP Server) with SMTP id 20F07300008B; Tue, 26 Oct 2010 10:19:30 +0200 (CEST) X-ME-UUID: 20101026081930135.20F07300008B@mwinf3j02.me.freeserve.com Received: (nullmailer pid 1595 invoked by uid 1000); Tue, 26 Oct 2010 08:19:50 -0000 Date: Tue, 26 Oct 2010 09:19:50 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <1287509041.022618.4884.nullmailer@galant.ukfsn.org> <1287561876.893861.6837.nullmailer@galant.ukfsn.org> <1287732977.227959.8695.nullmailer@galant.ukfsn.org> <1287738768.915002.8520.nullmailer@galant.ukfsn.org> <1287857292.298365.1038.nullmailer@galant.ukfsn.org> <1287874077.365931.1417.nullmailer@galant.ukfsn.org> <1287909035.704733.393.nullmailer@galant.ukfsn.org> <1288042690.562160.2361.nullmailer@galant.ukfsn.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1288081190.705299.12876.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp get failure 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: Tue, 26 Oct 2010 08:19:33 -0000 On Mon, 25 Oct 2010, Maksim Yevmenkin wrote: > i'm convinced that there is a bug in obexapp (or, less likely, > openobex library). it appears that "connection id" header is intended > for multiplexing of several data streams. its pretty much analog of > http "host" header. for what its worth, obexftp-0.20 exhibits the exact same behaviour as obexapp. (there are later versions but I can't be bothered to try and build them at this time, I have submitted patches to clean up Bluetooth support on *BSD over a year ago but the git repository shows no related activity) > i think its clear what "connection id" header must be present on all > requests from the client, including continue-GET request. what is not > entirely clear if the server responses should also contain "connection > id" header. i think they should as well. clearly, wm6 server is not > sending "connection id" header back in its responses, so perhaps its a > double whammy. Hm, are you saying that if the server included the Connection ID in its GET-response, would that make it to the continue-GET (because of OBEX_ObjectReParseHeaders() call)? iain