Re: Multiple connections, same port
- From: "Sharon" <nothing@xxxxxxxxx>
- Date: Thu, 2 Mar 2006 20:17:23 +0200
All clear, thanks a bunch.
Sharon.
"William Stacey [MVP]" <william.stacey@xxxxxxxxx> wrote in message
news:edyjDugPGHA.208@xxxxxxxxxxxxxxxxxxxxxxx
No, they can both send. Remember that have different sockets on the
server.
Tcp handles the retry logic, so it is not something you normally have to
deal with.
--
William Stacey [MVP]
"Sharon" <nothing@xxxxxxxxx> wrote in message
news:eCQ2vWePGHA.2888@xxxxxxxxxxxxxxxxxxxxxxx
| Ok, there is one more thing that is not clear to me.
| If 2 clients are connected on the same server ip & port,
| what happens when both clients try to send data at the same time?
| One of them waits until the other has finished sending?
| Thanks,
| Sharon.
|
|
| "William Stacey [MVP]" <william.stacey@xxxxxxxxx> wrote in message
| news:uChf2oZPGHA.3840@xxxxxxxxxxxxxxxxxxxxxxx
| > Yes, that is way it should work. Your client's would not know where to
| > connect if the port keeps changing on the server. As I said, there
are
4
| > pieces of information that make up a unique socket. only 1 has to be
| > different per socket. So the same client can connect multiple times
to
| > the
| > same server port as long as the client ports or different (dynamic).
Many
| > clients can connect to same server port because they all have
different
| > IPs,
| > etc. SMTP is port 25, DNS is 53 - they use wellknown server ports.
Does
| > that help?
| >
| > --
| > William Stacey [MVP]
| >
| > "Sharon" <nothing@xxxxxxxxx> wrote in message
| > news:edQKFoXPGHA.2704@xxxxxxxxxxxxxxxxxxxxxxx
| > | Hello William, and thanks for your reply.
| > | The listener socket always listens on the same port,
| > | but shouldn't a new worker socket be given a unique server port?
| > | In my app all clients use the same server listener port.
| > | In all examples i've seen about Socket async methods (BeginAccept,
| > | EndAccept),
| > | there is no attempt to switch the client port.
| > | Am i doing something wrong?
| > | By "yes" you mean that this is the way it should work?
| > | Sharon.
| > |
| > |
| > |
| > | "William Stacey [MVP]" <william.stacey@xxxxxxxxx> wrote in message
| > | news:uxBIlUXPGHA.516@xxxxxxxxxxxxxxxxxxxxxxx
| > | > Yes. Your server listens on same port, but the sockets are unique
| > (client
| > | > IP, client port, srv IP, srv Port).
| > | >
| > | > --
| > | > William Stacey [MVP]
| > | >
| > | > "Sharon" <nothing@xxxxxxxxx> wrote in message
| > | > news:eDKkJIXPGHA.1532@xxxxxxxxxxxxxxxxxxxxxxx
| > | > | Hi all,
| > | > | I've implemented a TCP server using the Socket async methods.
| > | > | When connecting to the server from 3 instances of hyper
terminal,
| > | > | i've noticed that each of the newly created server sockets, uses
the
| > | > same
| > | > | server port.
| > | > | I assumed that a new connection will receive a unique port.
| > | > | If this is the way its suppose to work, is it a performance
issue?
| > | > | Is it possible that connections from the same IP will connect on
the
| > | > same
| > | > | server port?
| > | > | I have no way to test it, as i have only one computer.
| > | > | Thanks,
| > | > | Sharon.
| > | > |
| > | > |
| > | >
| > | >
| > |
| > |
| >
| >
|
|
.
- References:
- Multiple connections, same port
- From: Sharon
- Re: Multiple connections, same port
- From: William Stacey [MVP]
- Re: Multiple connections, same port
- From: Sharon
- Re: Multiple connections, same port
- From: William Stacey [MVP]
- Re: Multiple connections, same port
- From: Sharon
- Re: Multiple connections, same port
- From: William Stacey [MVP]
- Multiple connections, same port
- Prev by Date: Could someone please write Design Patterns in C# for Dummies?
- Next by Date: Re: Connecting to DB2
- Previous by thread: Re: Multiple connections, same port
- Next by thread: Re: Multiple connections, same port
- Index(es):
Relevant Pages
|
