Re: RMI binding to SAME port but DIFFERENT IP address on SAME host
From: Esmond Pitt (esmond.pitt_at_notatall.bigpond.com)
Date: 07/29/04
- Next message: Andy Fish: "Re: Tomcat 5 with IIS6 using JK2"
- Previous message: Filip Larsen: "Re: Regular expressions"
- In reply to: Roedy Green: "Re: RMI binding to SAME port but DIFFERENT IP address on SAME host"
- Next in thread: Sam: "Re: RMI binding to SAME port but DIFFERENT IP address on SAME host"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 29 Jul 2004 08:55:30 GMT
Roedy
There is a protocol number field in an IP packet header, and I was
talking about IP at the time. Obviously in the case of TCP the protocol
number is the TCP protocol number, 6. BTW the statement that 'the host
computer simply knows which protocol it is hosting on each port' needs
further work. At the TCP level the host neither knows nor cares about
the protocol; at the IP level you *can* have several protocols on the
same port, e.g. ICMP, UDP, TCP.
EJP
Roedy Green wrote:
> On Thu, 29 Jul 2004 06:43:46 GMT, Esmond Pitt
> <esmond.pitt@notatall.bigpond.com> wrote or quoted :
>
>
>>hat's what it does, it can't do anything
>>else. A socket is identified by its IP address, its port number, and its
>>protocol number.
>
>
> I'm not sure if that is what you meant to imply, but there is no
> "protocol number" field in a TCP/IP header.
>
> see http://mindprod.com/jgloss/tcpip.html
>
> The host computer simply knows which protocol it is hosting on each
> port.
>
> You can't have two different protocols hosted on the same port, e.g.
> HTTP and FTP.
>
- Next message: Andy Fish: "Re: Tomcat 5 with IIS6 using JK2"
- Previous message: Filip Larsen: "Re: Regular expressions"
- In reply to: Roedy Green: "Re: RMI binding to SAME port but DIFFERENT IP address on SAME host"
- Next in thread: Sam: "Re: RMI binding to SAME port but DIFFERENT IP address on SAME host"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|