PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Noms de domaine > comp.protocols.tcp-ip > web server working urgent
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
comp.protocols.tcp-ip TCP and IP network protocols.

web server working urgent

Réponse
 
LinkBack Outils de la discussion
Vieux 17/05/2006, 12h46   #1
shan
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut web server working urgent

hi
i have a problem
see when we connect to any web server then according to http protocol
we connect on port 80 so when we connect to server on port 80 it
means that a socket is created on server which binds the port 80 with
let say to a client A Now the communication will be done by this
socket ( now this port will not used by any other socket) so when any
other client B will try to connect with the same server how it will
connect i mean the port is already occupied by this socket.
may be it is a stupid question but please answer this so that i can
clear the situation more
see what i am doing is i have created a server which is listening on
port 10000 now whenever a client tries to connect it it gets connected

(opens a socket) so now when any other client B trying to
connect on same port so is possible that server again get connected to

client B on this same socket ?????

  Réponse avec citation
Vieux 17/05/2006, 13h43   #2
Barry Margolin
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: web server working urgent

In article <1147866385.421764.281980@u72g2000cwu.googlegroups .com>,
"shan" <shan.icwa@gmail.com> wrote:

> hi
> i have a problem
> see when we connect to any web server then according to http protocol
> we connect on port 80 so when we connect to server on port 80 it
> means that a socket is created on server which binds the port 80 with
> let say to a client A Now the communication will be done by this
> socket ( now this port will not used by any other socket) so when any
> other client B will try to connect with the same server how it will
> connect i mean the port is already occupied by this socket.
> may be it is a stupid question but please answer this so that i can
> clear the situation more
> see what i am doing is i have created a server which is listening on
> port 10000 now whenever a client tries to connect it it gets connected
>
> (opens a socket) so now when any other client B trying to
> connect on same port so is possible that server again get connected to
>
> client B on this same socket ?????


A TCP connection is identified by four pieces of information: local
address, local port, remote address, and remote port. You can have
multiple connections with the same local address and port (port 80), but
they'll each have different remote address and/or remote port, so they
won't conflict with each other.

Run "netstat" on your server while multiple clients are connect and
you'll see all the different connections, each with different values in
the remote columns.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 07h05.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,07333 seconds with 10 queries