: Re: Final Confusions on Concurrent Server
The SELECT macro returns a bitmap of sockets, with the ones set to 1 (and
not 0) being the ones that been connected to (assuming the socket is a
listener socket). You simply do an ACCEPT of that socket. Your program I
would think already knows what
I thought he was looking for the server port, not the client port...?
On 11/4/2009 at 5:33 PM, Chuck Arney wrote:
> The Socket Address structure returned by ACCEPT contains the client port
> number of the connection you just accepted.
>>>
The information contained in this electronic communica
ember 04, 2009 7:34 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Final Confusions on Concurrent Server
>
> The SELECT macro returns a bitmap of sockets, with the ones set to 1 (and
> not 0) being the ones that been connected to (assuming the socket is a
> listener socket).
-MAIN@bama.ua.edu
Subject: Re: Final Confusions on Concurrent Server
I'm not sure I understand your question.
The server would normally LISTEN for incoming CONNECT requests
on a socket address that has been made "well known". For example,
this could be IPAddress 66.102.7.139 an
letion
>
> Of the ACCEPT) is never posted by TCP/IP
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
> Of J R
> Sent: Wednesday, November 04, 2009 4:55 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Final Confusio
.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of Joe Reichman
> Sent: Wednesday, November 04, 2009 5:41 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Final Confusions on Concurrent Server
>
> Sorry if I wasn'
rry if I've misunderstood.
===
> Date: Wed, 4 Nov 2009 12:17:11 -0500
> From: joereich...@optonline.net
> Subject: Re: Final Confusions on Concurrent Server
> To: IBM-MAIN@bama.ua.edu
>
> Is there a way for the server to know
Is there a way for the server to know what port the client is trying
to connect to
Sent from my iPhone
On Nov 4, 2009, at 9:59 AM, J R wrote:
Multiple concurrent connections between a client and server are
achieved by use of so-called "ephemeral ports" at the client end.
The port number
...@bama.ua.edu] On
Behalf Of J R
Sent: 04 November 2009 14:59
To: IBM-MAIN@bama.ua.edu
Subject: Re: Final Confusions on Concurrent Server
Multiple concurrent connections between a client and server are
achieved by use of so-called "ephemeral ports" at the client end.
The port number at
...@bama.ua.edu] On
Behalf Of J R
Sent: Wednesday, November 04, 2009 8:59 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Final Confusions on Concurrent Server
Multiple concurrent connections between a client and server are
achieved by use of so-called "ephemeral ports" at the client end.
The port
Email: rsc...@rs.com
Web: www.rocketsoftware.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
J R
Sent: 04 November 2009 14:59
To: IBM-MAIN@bama.ua.edu
Subject: Re: Final Confusions on Concurrent Server
Multiple concurrent connections
Multiple concurrent connections between a client and server are
achieved by use of so-called "ephemeral ports" at the client end.
The port number at the server end is predetermined and fixed so
that a client always knows where it has to connect to.
It is not necessary that the port
12 matches
Mail list logo
