Re: Purpose of rawsock module

Sam wrote:
> This module _IS_ that "socket library".

That was exactly what I needed to know :)


Reading the rest of the discussion, as well as what Don wrote:
> TCP/IP uses sockets but not raw sockets.

I think the name of the module is really unfortunate. "rawsock" could
plausibly mean all of the following:

* "raw access" to (the general concept of) sockets (which it actually is)
* access to OS specific sockets
* access to "raw sockets", i.e. SOCK_RAW

A better name would probably be something like BSD sockets, or even
POSIX sockets.


I wonder though, why is this not part of CLISP (i.e. not a module)?
The socket interface of CLISP could be perfectly well build on top of "rawsock",
or - if speed is an issue - on the underlying C functions.
Is the "overhead" of providing access to the functions (i.e. the LISP<->C
conversions, the additional subrs) really that crucial?

------------------------------------------------------------------------------
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