Thomas Davis <[EMAIL PROTECTED]> writes:
> On Thu, 02 Sep 1999, Dag Brattli wrote:
> >violation. I'll have to fix that as well. I'll try to make the IrDA socket
> >interface as close to the IrDA WinSock as possible (until I find a much
> >better way ;-)
> >
>
> does that include making IrCOMM work as a socket? (I noticed that the other
> day, when I was browsing MS's web site.. )
M$ thought that virtual serial ports would be confusing for their users. I
really don't think that this is a problem with Linux. IrCOMM is perhaps the
easiest thing to use with Linux ;-)
PPP will not run over sockets on Linux, so I see no reason to do something
like this. Other applications like the Pilot stuff, expect a serial port,
as well.
If you (or your application) want to use sockets instead of a serial port,
then you should just do that and not think of IrCOMM at all. IrCOMM will
just mean problems ;-) I expect that IrTranP will be fixed so it can run
directly over TinyTP. IrDA made a big mistake when they made IrTranP so
bounded to a specific transport (I guess they didn't have any alternative
at the time). But if you look at IrOBEX, you will see that it can run over
anything (even IrCOMM ;-)
If you really want a sockets interface for IrCOMM, I suggest you look at
the pilot-link package. They have made a sockets like library that wraps
over the serial port.
-- Dag
--
/ Dag Brattli | The Linux-IrDA Project /
// University of Tromsoe, Norway | Infrared communication for Linux //
/// http://www.cs.uit.no/~dagb | http://www.cs.uit.no/linux-irda/ ///
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
