From: Christopher Faylor <cgf-noreply@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Duplicating Unix Domain Sockets
Date: Mon, 03 Jun 2002 13:59:00 -0000 [thread overview]
Message-ID: <20020603205931.GC28699@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.30L.0206031633540.3061-100000@department-of-alchemy.mit.edu>
On Mon, Jun 03, 2002 at 04:47:49PM -0400, David E Euresti wrote:
>Allright. So I have two solutions.
>(And tell me if I should direct this to the folks at cygwin-devel)
>
>#1
>Make cygwin be able to implement the Ancillary data as in 4.3+BSD as
>described in section 15.3.3 in Advanced Programming in the Unix
>Environment.
>
>To implement this, I would tag all messages sent on Unix domain sockets
>with a tag like this:
>struct tag {
> int adatalen; // Length of ancillary data
> int rdatalen; // Length of real data
>}
>
>Then when you receive it your first read the tag and if there is ancillary
>data read it and do what you need to do (convert the info into an fd) and
>then read the rdatalen. If there is more rdatalen than the length of
>buffer sent to you, you return what you can, and remember how much is
>left.
>
>This is obviously a big task, and opinions would be quite welcome.
Sounds like it would slow down every UNIX domain socket read.
I'll let Egor comment on this, though. It's his code.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-06-03 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 13:52 David E Euresti
2002-06-03 13:59 ` Christopher Faylor [this message]
2002-06-03 23:17 ` egor duda
2002-06-04 5:41 ` Robert Collins
2002-06-05 12:30 ` David E Euresti
2002-06-04 8:07 ` David E Euresti
2002-06-04 8:33 ` egor duda
2002-06-04 8:40 ` David E Euresti
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 15:19 David E Euresti
2002-06-03 17:01 ` Bob Friesenhahn
2002-06-03 12:37 David E Euresti
2002-06-03 12:42 ` Christopher Faylor
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=20020603205931.GC28699@redhat.com \
--to=cgf-noreply@cygwin.com \
--cc=cygwin@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).