home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.internals
- Path: sparky!uunet!destroyer!gatech!hubcap!news
- From: rsaripa@venus.cs.clemson.edu (Saripalli Ramakrishna)
- Subject: Socket to which related processes may read/write ?.
- Message-ID: <1992Aug19.225324.21116@hubcap.clemson.edu>
- Sender: news@hubcap.clemson.edu (news)
- Organization: Clemson University Computer Science Dept.
- Distribution: na
- Date: Wed, 19 Aug 1992 22:53:24 GMT
- Lines: 34
-
- Hi ,
-
- I would like to know if there is any way a socket can be established
- by some ancestor so that all of its descendants might be able to
- monitor the socket(channel) and be able to read/write from/to the
- socket.
-
- I am specifically interested in sockets because my program uses
- recv() system calls(which I found very useful) and it works only
- on sockets(Even socketpair() would not work).
-
- I want to use recv() system calls because I want to peek at the
- incoming stream to retrieve the control information which always
- precedes the actual data .For instance,the control information
- contains the actual length(bytes) of the following message,the
- identity of the sender and some other relevant information.
-
- Of course,the length of the control information is constant across
- all messages.the processes would do recv() on the socket ,peek
- at the incoming stream(MSG_PEEK option of recv()) and remove from
- the stream messages relevant to themselves.
-
- I need this info very much.I went through Rich Stevens "Network
- Programming in Unix" but I was not able to find the relevant info.
-
- I would appreciate anyone who could send me this info.I will post
- to the group if there is enough interest.
-
- Thanks in advance,
- Saripalli Ramakrishna
-
- e-mail : rsaripa@cs.clemson.edu
-
- Man is a beast and usually has no control over his passions.
-