But all things considered, all this will simply lead to Apple ditching USB or layering a custom encrypted protocol on top of it. So Palm's current hack is a temporary solution.
How Palm Re-Enabled iTunes Sync
11–15 of 15 posts
Re: How Palm Re-Enabled iTunes Sync
#12Palm should've kept using their own USB ID and Manufacturer string, and allow users to override them to impersonate an arbitrary vendor. Including, of course, Apple. This way the Palm is in the clear, and it's the user that is responsible for the actual act of vendor/device impersonation. But all things considered, all this will simply lead to Apple ditching USB or layering a custom encrypted protocol on top of it. S…
Re: How Palm Re-Enabled iTunes Sync
#13Palm's confused if they think a compatibility check is a violation as opposed to, say, faking a hardware vendor ID. USB hardware IDs and network MAC addresses clearly have to respect the vendors' address spaces or the hardware standard falls apart.
Seems more likely this is a play to, yes, have the Palm device get press, but also ensure their site gets Page Rank from all the unique news articles' and blog entries' inbound links.
Re: How Palm Re-Enabled iTunes Sync
#14I'm still trying to figure out why iTunes only talking to iPod is (according to Palm) any more of a USB agreement violation than Nikon Capture only talking to Nikons, HP printer software only talking to HPs, or any other vendor software/vendor hardware combination that only works with the vendor's devices. Palm's confused if they think a compatibility check is a violation as opposed to, say, faking a hardware vendor…
Re: How Palm Re-Enabled iTunes Sync
#15I'm still trying to figure out why iTunes only talking to iPod is (according to Palm) any more of a USB agreement violation than Nikon Capture only talking to Nikons, HP printer software only talking to HPs, or any other vendor software/vendor hardware combination that only works with the vendor's devices. Palm's confused if they think a compatibility check is a violation as opposed to, say, faking a hardware vendor…
Hiding the codes/keeping them secret, like most vendors do, is okay -- the USB spec does not require disclosure.
BUT changing the codes to prevent interoperability is prohibited by the USB spec b/c it defeats the whole point of the USB spec.