On 2008-02-27, Micah Cowan <[EMAIL PROTECTED]> wrote:
> Grant Edwards wrote:
>> On 2008-02-26, Micah Cowan <[EMAIL PROTECTED]> wrote:
>>
>>> 7stud, what you seem to be missing, and what I'm not sure if anyone has
>>> clarified for you (I have only skimmed the thread), is that in TCP,
>>> connectio
Gabriel Genellina wrote:
> En Tue, 26 Feb 2008 07:53:24 -0200, 7stud <[EMAIL PROTECTED]>
> escribió:
>
>> ---
>> When you surf the Web, say to http://www.google.com, your Web browser
>> is a client. The program you contact at Google is a server. When a
>> server is run, it sets up business at a ce
Grant Edwards wrote:
> On 2008-02-26, Micah Cowan <[EMAIL PROTECTED]> wrote:
>
>> 7stud, what you seem to be missing, and what I'm not sure if anyone has
>> clarified for you (I have only skimmed the thread), is that in TCP,
>> connections are uniquely identified by a /pair/ of sockets (where
>> "
En Tue, 26 Feb 2008 07:53:24 -0200, 7stud <[EMAIL PROTECTED]>
escribió:
> ---
> When you surf the Web, say to http://www.google.com, your Web browser
> is a client. The program you contact at Google is a server. When a
> server is run, it sets up business at a certain port, say 80 in the
> Web c
In article
<[EMAIL PROTECTED]>,
7stud <[EMAIL PROTECTED]> wrote:
> If two sockets are bound to the same host and port on the server, how
> does data sent by the client get routed? Can both sockets recv() the
> data?
Undefined.
You certainly won't find the answer in the RFCs which define the p
On 2008-02-26, Micah Cowan <[EMAIL PROTECTED]> wrote:
> 7stud, what you seem to be missing, and what I'm not sure if anyone has
> clarified for you (I have only skimmed the thread), is that in TCP,
> connections are uniquely identified by a /pair/ of sockets (where
> "socket" here means an address
Hrvoje Niksic wrote:
> 7stud <[EMAIL PROTECTED]> writes:
>
>> When you surf the Web, say to http://www.google.com, your Web browser
>> is a client. The program you contact at Google is a server. When a
>> server is run, it sets up business at a certain port, say 80 in the
>> Web case. It then wait
7stud wrote:
> On Feb 25, 10:00 pm, Roy Smith <[EMAIL PROTECTED]> wrote:
>> In article
>> <[EMAIL PROTECTED]>,
>>
>> 7stud <[EMAIL PROTECTED]> wrote:
>>> But your claim that the server doesn't change its port flies in the
>>> face of every description I've read about TCP connections and
>>> accept
7stud wrote:
>
> If two sockets are bound to the same host and port on the server, how
> does data sent by the client get routed? Can both sockets recv() the
> data?
I have learned a lot of stuff I did not know before from this thread,
so I think I can answer that.
There must be a layer of sof
7stud <[EMAIL PROTECTED]> writes:
> When you surf the Web, say to http://www.google.com, your Web browser
> is a client. The program you contact at Google is a server. When a
> server is run, it sets up business at a certain port, say 80 in the
> Web case. It then waits for clients to contact it.
On Feb 25, 10:00 pm, Roy Smith <[EMAIL PROTECTED]> wrote:
> In article
> <[EMAIL PROTECTED]>,
>
> 7stud <[EMAIL PROTECTED]> wrote:
> > But your claim that the server doesn't change its port flies in the
> > face of every description I've read about TCP connections and
> > accept(). The articles a
On Feb 25, 10:08 pm, Steve Holden <[EMAIL PROTECTED]> wrote:
> There can be many TCP connections to a server all using the same
> endpoint. Take a look at the traffic coming out of any busy web server:
> everything that comes out of the same server comes from port 80. That
> doesn't stop it listeni
Roy Smith wrote:
> In article <[EMAIL PROTECTED]>,
> Steve Holden <[EMAIL PROTECTED]> wrote:
>
>> TCP guarantees
>> that no two ephemeral port connections from the same client will use the
>> same port.
>
> Where "client" is defined as "IP Address". You could certainly have a
> remote machi
In article <[EMAIL PROTECTED]>,
Steve Holden <[EMAIL PROTECTED]> wrote:
> TCP guarantees
> that no two ephemeral port connections from the same client will use the
> same port.
Where "client" is defined as "IP Address". You could certainly have a
remote machine that has multiple IP addresse
7stud wrote:
> On Feb 25, 10:56 am, Thomas Bellman <[EMAIL PROTECTED]> wrote:
>> 7stud <[EMAIL PROTECTED]> wrote:
>>> The question I'm really trying to answer is: if a client connects to a
>>> host at a specific port, but the server changes the port when it
>>> creates a new socket with accept(), h
In article <[EMAIL PROTECTED]>,
"Gabriel Genellina" <[EMAIL PROTECTED]> wrote:
> En Mon, 25 Feb 2008 20:03:02 -0200, 7stud <[EMAIL PROTECTED]>
> escribió:
> > On Feb 25, 10:56 am, Thomas Bellman <[EMAIL PROTECTED]> wrote:
> >> 7stud <[EMAIL PROTECTED]> wrote:
>
> > In either case, there are st
In article
<[EMAIL PROTECTED]>,
7stud <[EMAIL PROTECTED]> wrote:
> But your claim that the server doesn't change its port flies in the
> face of every description I've read about TCP connections and
> accept(). The articles and books I've read all claim that the server
> port 5053 is a 'listeni
En Mon, 25 Feb 2008 20:03:02 -0200, 7stud <[EMAIL PROTECTED]>
escribió:
> On Feb 25, 10:56 am, Thomas Bellman <[EMAIL PROTECTED]> wrote:
>> 7stud <[EMAIL PROTECTED]> wrote:
> In either case, there are still some things about the output that
> don't make sense to me. Why does the server initiall
On 2008-02-25, 7stud <[EMAIL PROTECTED]> wrote:
> On Feb 25, 10:56 am, Thomas Bellman <[EMAIL PROTECTED]> wrote:
>> 7stud <[EMAIL PROTECTED]> wrote:
>> > The question I'm really trying to answer is: if a client connects to a
>> > host at a specific port, but the server changes the port when it
>> >
On Feb 25, 10:56 am, Thomas Bellman <[EMAIL PROTECTED]> wrote:
> 7stud <[EMAIL PROTECTED]> wrote:
> > The question I'm really trying to answer is: if a client connects to a
> > host at a specific port, but the server changes the port when it
> > creates a new socket with accept(), how does data sen
7stud <[EMAIL PROTECTED]> wrote:
> The question I'm really trying to answer is: if a client connects to a
> host at a specific port, but the server changes the port when it
> creates a new socket with accept(), how does data sent by the client
> arrive at the correct port? Won't the client be sen
On Feb 25, 5:17 am, 7stud <[EMAIL PROTECTED]> wrote:
> On Feb 25, 4:08 am, 7stud <[EMAIL PROTECTED]> wrote:
>
>
>
> > The question I'm really trying to answer is: if a client connects to a
> > host at a specific port, but the server changes the port when it
> > creates a new socket with accept(), h
>
> The question I'm really trying to answer is: if a client connects to a
> host at a specific port, but the server changes the port when it
> creates a new socket with accept(), how does data sent by the client
> arrive at the correct port? Won't the client be sending data to the
> original por
On Feb 25, 4:08 am, 7stud <[EMAIL PROTECTED]> wrote:
>
> The question I'm really trying to answer is: if a client connects to a
> host at a specific port, but the server changes the port when it
> creates a new socket with accept(), how does data sent by the client
> arrive at the correct port? Wo
On Feb 25, 2:43 am, [EMAIL PROTECTED] wrote:
>
> by reusing the same variables without storing the previous values.
> This could make the Python
> garbage collector to attempt freeing the socket object created with
> the first connection, therefore
> closing the connection.
>
> If I'm right, your p
On Feb 25, 2:43 am, [EMAIL PROTECTED] wrote:
> On 25 Feb, 09:51, 7stud <[EMAIL PROTECTED]> wrote:
>
>
>
> > I have the following two identical clients
>
> > #test1.py:---
> > import socket
>
> > s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>
> > host = 'localhost'
> > port = 5052
On 25 Feb, 09:51, 7stud <[EMAIL PROTECTED]> wrote:
> I have the following two identical clients
>
> #test1.py:---
> import socket
>
> s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>
> host = 'localhost'
> port = 5052 #server port
>
> s.connect((host, port))
> print s.getsockname()
I have the following two identical clients
#test1.py:---
import socket
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
host = 'localhost'
port = 5052 #server port
s.connect((host, port))
print s.getsockname()
response = []
while 1:
piece = s.recv(1024)
if piece == '':
28 matches
Mail list logo
