At 9:48 PM -0500 2/3/00, Belal Tassi wrote:
>1) My first question is if PALM OS 3.0's irda is fully OBex compliant. I am
>planning to develop an embedded system that communicates with a PALM III
>over the irda port. Can I just implement OBex on the embedded device and
>then go ahead and use the Exchange Manager to talk to it on the palm
>side(back and forth of course)? This was my original assumption but then I
>came across this confusing statement in the Programmer's Companion:
>
>NOTE: ..The only level of OBEX supported currently is for the Put
>operation. (pg 226)
> 
>
>Does this mean that the Get funtions are not OBex compliant?

When a Palm beams data using the Exchange Manager, it does a single PUT operation. The 
instigator is also the sender. The Exchange Manager does not currently support doing a 
CONNECT followed by data flowing in both directions. It doesn't even support doing a 
GET, where the instigator only receives data. We recognize that this limitation is a 
concern for our developers.

>2) Does anyone know where I can get sample code to help me learn how to use
>the ir library? I am having trouble finding this (although the exchange
>manager examples are plenty.)

Check out IR Ping. I'm not sure where it is, but check road coders, PalmGear, etc.

I needed to do two-way IR communication in BeamBooks, so I wrote a layer on top of the 
IR Library to provide a UI and API along the lines of the Exchange Manager. I made no 
attempt to make it OBEX compliant since I was communicating with another device 
running BeamBooks.

Perhaps IrCOMM would work for you. You give up control over how the connection is 
made, but you have a 2-way streaming interface once it's up. Or you can do what I did 
for BeamBooks and use your own protocol on top of TinyTP on both the Palm and the 
embedded device.
-
Danny Epstein - Applied Thought
No Palm is an Island - try BeamBooks
http://www.appliedthought.com/beambooks

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palm.com/devzone/mailinglists.html

Reply via email to