a Small doubt whith the Port Number

Thread View: borland.public.cppbuilder.internet.socket

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by McKool Mon, 12 Jul 2004 14:01

#5713

Author: McKool
Date: Mon, 12 Jul 2004 14:01

20 lines
1684 bytes

Hello.  Yes, i have a small doubt.  I know that the ports smaller than 1024
are "reserved or standard ports", a mean, in this range are the ports number
defined for knew task like FTP, HTTP, etc etc.  I made an application and i
use only port numbers grater than 1023.  I'm just want to be sure that i
have all in the right way.

- What do i have  to keep in mind in selecting the port number that my
application should use? I mean, I tested my application with port 80 and it
works, port 7 and it works, etc etc.

- Can affect the speed of sending data depending of the port number?

-  Since my applicaiton is used transmit using my own protocol,  without
follow a defined knew protocol like HTTP, would be a good idea to take a
port greater than 1024 or is just the same which port  i take to make my
communication?.

Thanks in advance.

Keneth Wagner.

Re: a Small doubt whith the Port Number

#5714

Author: Remy Lebeau (TeamB)
Date: Mon, 12 Jul 2004 16:35

31 lines
1976 bytes

"McKool" <kenethw@peak-system.com> wrote in message
news:40f2998c@newsgroups.borland.com...

> - What do i have  to keep in mind in selecting the
> port number that my application should use?

Make sure that no other application on the machine is using the same port(s)
that you are.  Also, if on a network and/or a firewall or router is
involved, make sure the port(s) are accessible.

> I mean, I tested my application with port 80 and
> it works, port 7 and it works, etc etc.

Just because they are "reserved" doesn't mean that can't work in general,
just as long as they are not already in use.

> - Can affect the speed of sending data depending of the port number?

No.

> -  Since my applicaiton is used transmit using my own protocol,
> without follow a defined knew protocol like HTTP, would be a
> good idea to take a port greater than 1024 or is just the same
> which port  i take to make my communication?.

If you are designing your own protocol, it is best to use your own port
number as well.  Less chance of conflict that way.


Gambit

Re: a Small doubt whith the Port Number

#5719

Author: McKool
Date: Tue, 13 Jul 2004 06:10

38 lines
2228 bytes

Thansk gambit.

"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> schrieb im
Newsbeitrag news:40f2bdc0$3@newsgroups.borland.com...
>
> "McKool" <kenethw@peak-system.com> wrote in message
> news:40f2998c@newsgroups.borland.com...
>
> > - What do i have  to keep in mind in selecting the
> > port number that my application should use?
>
> Make sure that no other application on the machine is using the same
port(s)
> that you are.  Also, if on a network and/or a firewall or router is
> involved, make sure the port(s) are accessible.
>
> > I mean, I tested my application with port 80 and
> > it works, port 7 and it works, etc etc.
>
> Just because they are "reserved" doesn't mean that can't work in general,
> just as long as they are not already in use.
>
> > - Can affect the speed of sending data depending of the port number?
>
> No.
>
> > -  Since my applicaiton is used transmit using my own protocol,
> > without follow a defined knew protocol like HTTP, would be a
> > good idea to take a port greater than 1024 or is just the same
> > which port  i take to make my communication?.
>
> If you are designing your own protocol, it is best to use your own port
> number as well.  Less chance of conflict that way.
>
>
> Gambit
>
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads