Re: More details on OBEX FTP trouble - solved
Re: More details on OBEX FTP trouble - solved
- Subject: Re: More details on OBEX FTP trouble - solved
- From: Thomas Tempelmann <email@hidden>
- Date: Tue, 03 Apr 2007 11:13:49 +0200
- Thread-topic: More details on OBEX FTP trouble - solved
On 3.4.2007 2:09 Uhr, "Bubba Giles" <email@hidden> wrote:
> OBEXSample was not supposed to be an FTP client, which is why it
> doesn't work that way. It is supposed to be an OPP sample only.
Are you sure you're not confusing the sample "OBEXSample" with
"OBEXSampleSendVCard"?
Or why does "OBEXSample" have an implementation and UI for setting a Path? I
thought OPP does not provide SETPATH, only FTP does? (i.e. searching for
"path" in the OPP 1.1 spec does not find anything)
And the implementation of the SETPATH function is still using the wrong flag
no matter what.
Furthermore, while the GET method provides for receiving the default vCard
as doc'd in the OPP spec, it _also_ allows to retrieve arbritrary files,
which is a feature of FTP, not OPP, as far as I understand. Please clarify.
So my conclusion remains: The sample does not obey the Spec, and should be
fixed therefore (as reported in bug #5095147).
Or, at least, _document_ its purpose. If it's really meant to show how OPP
works, then please write that down there. Refer to the specs, for instance.
Or, name it "OPPSample", not "OBEXSample".
Really confused,
Thomas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden