From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Cc: khaled@pacificpost.com
Subject: Re: Presentation Layer in TCP/IP linux implementation
Date: Wed, 20 Dec 2000 05:02:21 +0100 [thread overview]
Message-ID: <E148aSL-0001cH-00@calista.inka.de> (raw)
In article <3A3F57A0.32A6F34D@pacificpost.com> you wrote:
> Hello Linux World,
> Is there a way to add a generic and transparent presenation layer in the
> path of TCP/IP packets. I am speaking about something probably in the
> path between the user space mechanims (send/recv/read/write) and the
> actual sock_sendmsg/sock_recvmsg (and their proto counterparts).
In User mode you can use a dynamically pre-loaded lib, like socks is doing.
Greetings
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-20 4:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 4:02 Bernd Eckenfels [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 12:42 Presentation Layer in TCP/IP linux implementation khaled
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E148aSL-0001cH-00@calista.inka.de \
--to=ecki@lina.inka.de \
--cc=khaled@pacificpost.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox