1. Palm devices are marginally IrDA compliant. There are some timing requirements
that are not followed strictly. Also, it is too simple for a developer to make
the device break the IrDA protocols due to the fact that the IR code runs in
the same thread as the application and can't get the processor when it needs it.
(BTW...this is different from the network library which has its own thread)
2. Palm devices don't talk IrOBEX by "default". The built-in apps happen to support
IrOBEX. Both the Exchange Manager (IrOBEX) and the TTP/IrLMP API's are
accessible to developers.
3. It has been my experience that using IR with non-Palm devices is not
easily done. Connecting (at the IrLMP layer) to various laptops via IR
has been unreliable at best (granted, due in part to Microsoft's and the
laptop manufacturer's dubious IR implementations); a race condition (bug) exists
in the Palm III IR stack that makes my application incapable of connecting to
all but the most forgiving of passive devices; similar frustrations exist
with WinCE devices, digital cameras, and cellular phones. There's a whole
ecosystem out there beyond Palm's and printers and laptops. And the IR
connectivity is not there. Hence my interest in Palm's extending their
'official' support beyond other PalmOS devices.
4. Installing IrOBEX on other devices does not solve the interoperability
problem. It merely moves the problem further up the protocol stack to the
application layer. With IrOBEX I can still receive data I can't do anything
with (similar to getting an AmiPro document via email and not being able
to read it). This is not my idea of a seamless use model.
5. For years IrDA has been trying to steer people away from IrCOMM. It takes
over the whole link and IrLMP, which is there to provide session multiplexing, is
useless when IrCOMM is active. Doesn't make much difference to a PalmOS
device since it is 'single-tasking' but Palm supporting IrCOMM means devices it
is talking to must be dedicated to that session.
Adrian Pfisterer.
Hewlett-Packard.
> Date: 29 Apr 1999 09:17:45 -0700
> From: Ade Barkah <[EMAIL PROTECTED]>
> Subject: Re: transmitting data by IR
>
> Palm devices are actually IrDA DATA compliant. However, by default they
> talk the IrOBEX protocol, not the IrCOMM protocol used in most peripherals.
> The solution is simple: either install IrOBEX on the other devices (there
> are free implementations for the PC) or install IrCOMM support on the Palm,
> from the Enhanced Infrared Update:
>
> http://www.palm.com/custsupp/downloads/irenhanc.html (*)
>
> In any case, using IR with non-Palm devices can be easily done.
>
