site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com jason On Apr 3, 2007, at 2:13 AM, Thomas Tempelmann wrote: On 3.4.2007 2:09 Uhr, "Bubba Giles" <bubba@apple.com> 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"? Really confused, Thomas _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... Actually, now that I reflect on it more, OBEXSample was written to show how to use Apple's OBEX API. Thus, it implements most of the commands in the OBEX spec, not those specifically found in a Bluetooth profile such as OPP or FTP. It was not really meant as a way to show you how to fully implement a proper FTP client, or an OPP client. Not to mention it was written years ago, when OBEX was first implemented on the stack (that is not an excuse just a reality). Besides, the developer samples are provided a starting point, not the end-all be-all of how to do something (which is why there is a gigantic disclaimer at the top). We'll try to fix the erroneous setpath flag. 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". This email sent to site_archiver@lists.apple.com