Boost logo

Boost :

From: Pavol Droba (droba_at_[hidden])
Date: 2002-11-26 03:22:26

On Mon, Nov 25, 2002 at 04:09:29PM +0000, Hugo Duncan wrote:
> Pavol,
> On Sun, 24 Nov 2002 10:12:36 +0100, Pavol Droba <droba_at_[hidden]> wrote:
> > Is there an interest to support also non-TCP/IP based protocols like
> > IRDA/TP or raw sockets?
> I think this should be feasable, though I know nothing of IRDA/TP.
> Is it just a case of using the appropriate sockaddr_?? class
> and protocol constants? Or are there any requirements on the
> communciation once connection is established?
> Hugo
Well IRDA/TP was just an example. There are few differences in the initialization
of the socket and of course the different socketaddr. What I was trying to ask
is if it would be feasible to add a specializations for non standard protocols.

I think its a good idea to leave the design open.

If you need examples about different protocols, try to check out MSDN. Winsockets
have support for almost every protocol in win platform including NetBEUI, IPX, IRDA/TP
and probably more.

It could be maybe interesting to look into design of winsockets. There is something
called TDI layer in the windows kernel which works as an interface between high-level
sockets and kernel-mode drivers. Its design is pretty flexible to support all socket
protocol types

Maybe it could be worth to look at it to get some ideas how to design lower layers of
socket lib.

Just my thoughts :)



Boost list run by bdawes at, gregod at, cpdaniel at, john at