> I'm not sure it's "worse" since the legacy connection type is required for
> all supported pre-WM5 devices anyway. In addition, connection via BT is
> supported, which, AFAIK, is essentially serial in nature as well.
>
> Given the number of issues we see with AS/WMDC on this NG, I suspect
> keeping multiple connection methods around is probably the least of their
> problems!
Bluetooth code can be written using the serial programming interface, or the
networking one. I'd think that they're probably using the network scheme.
You'd think that they wouldn't have to put effort into the non-networking
communication on the device for new devices, though, if the network
interface really worked reliably in the field. If they just needed to
support the old devices with the old comm methods, all the effort would be
on the PC side. Now, they have the effort on both sides for new devices, as
well as testing both comm methods with both new and old devices.
Paul T.