On Sat, 11 Oct 2008, Robert Elz wrote:
quoted text
> I'd suggest that the API (and hence the name) should be independent of
> any suggestion of transport technology (so should not involve IR) - there's
> no reason a bluetooth remote, or a 802.15 remote, or anything else
> (including 802.3, or RS232) should present a different interface to the
> application, it is the function the application cares about, not the
> signalling technique by which the user supplies that information to
> the system.

It depends what you mean by application. As I have stated before in this 
thread, /dev/remote isn't intended for direct use by the application that 
processes commands, they instead should talk to the userspace daemon which 
handles keymappings.

Jared