Subject: | |
From: | |
Reply To: | |
Date: | Fri, 31 Jan 2003 09:41:23 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
However, what Keven quoted is in direct conflict with the
following:
IPCCREATE
opt (input)
maximum connection requests queued (option code=6,
length=2,...). Used to specify the maximum number of
unreceived connections that can be queued to a call
socket. The default is 7.
I would also like to add that not ALL features of NetIPC
are documented or documented correctly. Here are some
undocumented features/differences that I find handwritten
in my copy of the manual:
IPCCREATE
User mode programs can use any port value regardless of what
the documentation states. BTW - QWEBS uses port 80 and it has
NO pm code.
IPCDEST
opt (input)
To specify an IP address as the destination use code=16
with a 6 byte option value of '08' + 4-byte ip address in
byte/binary format.
IPCRECV
Additional errors not mentioned that can occur: 64, 68
IPCRECVCN
Additional errors not mentioned that can occur: 64
duane percox
> -----Original Message-----
> From: Keven Miller [mailto:[log in to unmask]]
> Sent: Wednesday, January 29, 2003 8:41 AM
> To: John Korb; [log in to unmask]
> Subject: Re: [HP3000-L] IPCRecvCn Question
>
>
>
> Here is some text from IPCRECVCN. Note the last sentance.
>
> Description
> The IPCRECVCN intrinsic allows a process to receive a connection
> request and establish a connection (virtual circuit). The
> connection is
> identified by the returned VC socket descriptor. The calling
> process can
> then employ the IPCSEND and IPCRECV intrinsics to send and receive
> data on the connection. A maximum of one unreceived connection
> request may be queued to a call socket.
>
> I was thinking there was a way to change it like with the bsd
> call listen
> ( s, n ) where n is
> the queue size. This may be why I choose (I can't remember
> that far back;
> and yes,
> I still have docuphobia of sorts as do all programmers) for
> my server to
> have a son
> process (or processes) that does the (in my case, RPMCREATE) process
> creation
> and handing off the socket.
> I use a msgfile between the two for passing the socket name,
> so the names
> can queue up
> from the parent process.
>
> Some pseudo pseudo-code.
> Parent
> -------
> Create sons
> create listen socket
> Loop:
> IPCRECVCN
> get socket name or give it one
> IPCGIVE
> write name to msgfile
> goto loop
>
> Son
> ------
> open msgfile
> loop:
> read msgfile
> IPCGET
> IPCGIVE
> RPMCREATE or CRAETEPROCESS with INFO containing socket name
> IF create error
> IPCGET
> IPCSHUTDOWN
> ENDIF
> goto loop
>
>
> Keven Miller
> [log in to unmask]
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|