Re: Test Availability of TCP Port?
From: Jon Skeet [C# MVP] (skeet_at_pobox.com)
Date: 02/10/04
- Next message: Houston Keach: "System.InvalidOperation Exception"
- Previous message: Scott M.: "Re: script not running"
- In reply to: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Next in thread: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Reply: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Feb 2004 18:22:28 -0000
William Stacey [MVP] <staceywREMOVE@mvps.org> wrote:
> > No. I'm talking protocol such as NNTP, SMTP etc - except probably one
> > specifically for your application.
>
> Ok. Now I understand. I would agree with this. If you want to offer
> different services like SMTP, FTP, etc on the same server process, then that
> would be natural. I did not see that in his post. Maybe some more detail
> from Kevin as what exactly he is trying to do would be helpful at this
> point.
I wasn't particularly addressing Kevin's particular request - more the
general "is it ever useful" point which you didn't really make in the
first place :)
> > Where exactly did I say that ports aren't limited?
>
> Sorry, typo. "as fixed port numbers are limited" Meant to say "are"
> limited. That is how this started I think.
Possibly. Along those lines, by the way - I reckon port numbers ought
to actually be UTF-8 strings. That way it wouldn't be too hard to
pretty much guarantee that no-one else was using your port. There are
problems involved with that (there'd need to be a length limit etc) but
it would really help, IMO...
> > I must have interpreted your "no self respecting server program [...]
> > uses ports in that manner" post overly widely then.
>
> Kinda. We did not start out talking about different protocols like smtp,
> nntp in the *same server service. These are normally provided by different
> services. Again, I think we need some clarity on exactly what Kevin is
> trying to do here. Kevin, if you still want to discuss, could we have a bit
> more detail?
Just to clear up my protocol business - I wasn't talking about wildly
different standard protocols, I was talking about a single overall goal
which involved various different network protocols inside, which might
naturally fit on multiple ports. FTP is (IIRC) a good example of this,
with one protocol for the control, and another for the data streaming.
-- Jon Skeet - <skeet@pobox.com> http://www.pobox.com/~skeet If replying to the group, please do not mail me too
- Next message: Houston Keach: "System.InvalidOperation Exception"
- Previous message: Scott M.: "Re: script not running"
- In reply to: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Next in thread: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Reply: William Stacey [MVP]: "Re: Test Availability of TCP Port?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|