Re: Adding a new OSI layer

Hi,

Not quite: you could easily add another library and then require such
applications (or their users) to LD_PRELOAD such a library. Haven't
tried that, though.
But it should work, as efence uses that to force an application to use
modified malloc/free functions. I guess that the socks package does so, too.
Maybe you'd have to use a few tricks to call the "standard" socket() and
friends but that could be solved as well. Maybe you'd really look at
socks. Haven't used that, though, too.
Ok, so you could do migration with an user space only solutions as
well.

But - given this fiftth layer would be something important and useful
and requires adding protocol headers to the transport layer headers -
I guess that it should belong to the OS (kernel).

Cheers
Christian

.