site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com User-agent: Microsoft-Entourage/9.0.4.4011 Phil wrote at Fri, 24 Sep 2004 18:32:50 +1200
I'm working on writing a simple SyncML client to operate over OBEX
You'll write a SyncML server. The phone is the SyncML client. ;-) The other way around than in IrDA IrMC Level 4. BTW this is not a newbie question - it is quite an advanced OBEX question. You have understood a lot already! I hope you still read this mailing list. Phil wrote at Fri, 24 Sep 2004 18:32:50 +1200
I can select a Bluetooth Device (specifically, a Nokia 7610) and make an OBEX connection to it [...] but the OBEXConnectCommandResponseData I get back has no header
Are you connecting to the OBEX Push Bluetooth profile? For the Nokia 7610 you have to connect to the "Client SYNCML" Bluetooth profile. Only this profile will allow SyncML over OBEX - do not ask me why Nokia made it this way. For further reading this should be quite complete: http://discussion.forum.nokia.com/forum/showthread.php?threadid=44303 I have done the same here on my Nokia 6820 but I never played with Apple's OBEX implementation because I have my own. I wouldn't even recommend Apple's version - as far as I know it is tight to Bluetooth only - correct me here if I am wrong. Anyway the Nokia has implemented a separate OBEX server only for SyncML (they seem to have to much man power) but this one is very very buggy at least here in my Nokia 6820. It does not follow most OBEX recommendations and even rejects most things with a reboot of the phone. A basic OBEX implementation is written quite fast - so if you fail go for your own implementation which you can tweak for the Nokia SyncML over OBEX server. I wonder why are you going for a SyncML over OBEX implementation. I am quite sure Apple iSync will support SyncML 1.1.2 over OBEX quite soon (my estimate is around Christmas). As 100% direct competitor your product won't be accepted anymore. Bubba Giles wrote at Mon, 27 Sep 2004 09:56:00 -0700
SYNCML-SYNC The example value for the Target header can be IRMC-SYNC¹ to indicate the IrMC synchronization service.
The Nokia 7610 has Open Mobile Alliance's SyncML Data Synchronization version 1.1.2 over OBEX which must be called via the "SYNCML-SYNC" UUID in the OBEX Connect Target header. It is not an official Bluetooth SIG profile but this is specified within SyncML itself. The Nokia 7610 does not have IrMC over Bluetooth nor does it have SyncML over mRouter which is used by Apple iSync for other (older) Symbian OS mobile phones. Bubba Giles wrote at Mon, 27 Sep 2004 09:56:00 -0700
The spec can be a maze, indeed.
- OBEX 1.3 http://www.irda.org/displaycommon.cfm?an=1&subarticlenbr=7 - Binding for SyncML 1.1.2 over OBEX http://www.openmobilealliance.org/release_program/enabler_releases.html#ds2 are quite good to read. I have seen worse specifications. These two documents have a lot of examples which even are correct. The rest of SyncML is terrible to read and is buggy. =( _______________________________________________ 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... This email sent to site_archiver@lists.apple.com