From owner-freebsd-bluetooth@FreeBSD.ORG Fri Oct 29 11:00:54 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 D3FEB106566B for ; Fri, 29 Oct 2010 11:00:54 +0000 (UTC) (envelope-from plunky@galant.ukfsn.org) Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10]) by mx1.freebsd.org (Postfix) with ESMTP id 68CF48FC17 for ; Fri, 29 Oct 2010 11:00:54 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id A5033DEBDC; Fri, 29 Oct 2010 12:00:52 +0100 (BST) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id fkEHFjlUiABE; Fri, 29 Oct 2010 12:00:52 +0100 (BST) Received: from galant.ukfsn.org (unknown [87.242.154.254]) by mail.ukfsn.org (Postfix) with ESMTP id 4C568DEB85; Fri, 29 Oct 2010 12:00:52 +0100 (BST) Received: by galant.ukfsn.org (Postfix, from userid 1000) id DECC9260260; Fri, 29 Oct 2010 12:01:14 +0100 (BST) Date: Fri, 29 Oct 2010 12:01:14 +0100 (BST) From: Iain Hibbert To: Maksim Yevmenkin In-Reply-To: Message-ID: References: <1287509041.022618.4884.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> <1288081190.705299.12876.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 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: Fri, 29 Oct 2010 11:00:54 -0000 On Thu, 28 Oct 2010, Maksim Yevmenkin wrote: > > One thing that I can't check, what would happen if the "obexapp client GET > > -> remote" session get response did contain a Connection ID already, > > would we send it twice? > > i'm not sure... i'm tempted to say no because header are parsed, i.e. > we effectively move headers to another list (that is why we need > reparse call). however, this is something that openobex library does > internally, so, we need to test it. I thought about this and maybe it is a little clearer .. the object that is handed to the stream read/write functions is in fact the base GET/PUT command that openobex thinks we should be sending.. so it should be up to us to add any Connection ID headers since openobex doesn't know about them > would be really nice to try it again apple mac os x. those guys usually > do things according to standards :) obexapp works against Mac OS X 10.6 (see 2.5Mb log of get and put with connections from either side at www.netbsd.org/~plunky/obexapp-macos.txt) I also tried my wm6 phone against it and it works fine too but I don't have a packet sniffer on the mac iain