From: Philip K. <kov...@co...> - 2005-09-08 22:53:39
|
Christian, I forgot to mention that the ordering of the headers is important and this is stated as such in the BT spec: the connection id header must come first . Just so you know as you work with the code. I would also consider a run-time config file, e.g. .obexftp, to serve as permanent storage for params we're always going to use: ---- ./.obexftp ---- bluetooth=<address> channel=<channel no> connection_id_headers=yes etc. Phil Christian W. Zuckschwerdt wrote: > Hi Phil, > > so it's about the connection id then. Exactly the piece that was > missing, great work! > Your patch is a clean base to work from. I think I'll make it a > command line option and not just a compile time flag though. > > Thank you for the hard work, again. > > cu, > Christian > > Philip Kovacs wrote: > >> Conforming more strictly to the Bluetooth 1.1 spec, the client is >> supposed to retain the connection id and return it to the server >> within an OBEX connection header with each OBEX command the client >> sends. > > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Openobex-users mailing list > Ope...@li... > http://lists.sourceforge.net/lists/listinfo/openobex-users > |