You are right, you can bind to different ports using TinyTP. In my previous post, I simplified the actual layers of IrDA just to explain that IrCOMM and OBEX (actually IrOBEX) were different. The actual layers (as you've alluded to) are:

1. IrPHY (physical layer)
2. IrLAP (data link)
3. IrLMP (data link)
4. IrTTP (Tiny TP)
5. IrCOMM or IrOBEX

Yes, it would be possible to code Empire to handle both, and to code Palantir with a terminal app, but it would be a huge programming job to finish, and you are probably the only one on the board that has the expertise to tackle the job! I am using the OpenOBEX libraries to do all of my protocol work for me, and I would not attempt this feat. I was thinking that a simple solution would be to switch control over to another program, since we already know how to create an IrCOMM connection. The user would be using different Palm apps anyway, and the physical link would go down, since the user would have to switch apps to a terminal program on the Palm, and that would disconnect the session.