Purpose of rawsock module

I'm currently working on getting the rawsock module up-to-date and running
on the major target platforms. I got a bit unsure about the real purpose,
the "goal" of that module, though:

The documentation suggests that it's providing access to what sys/socket.h
provides, i.e. "raw" access to sockets.

Windows doesn't have sys/socket.h, but rather WinSock2. While there are
a lot of similarities between those (IIRC that was one of the design goals
of WinSock) they're certainly different in some parts.
(I guess this is mostly due to sockets not being guaranteed to be file handles
and the way one does asynchronous IO)

Unifying both sys/socket.h and WinSock2 behind the same interface seems to
be a contradiction to the "raw" access to me, though. If that's the goal
of the module, wouldn't it be much better to have a module providing access
to some "socket library"?

Or would it be useful to split the rawsock module in platform dependent
modules, just like it's done with bindings/glibc and bindings/win32?

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel