🚀 go-pugleaf

Hi John,

Let me run this by you.  Does it make sense to use a particular port as a
shared resource for a particular purpose?  In my case, I have my server app
where I want to make available a particular port that clients can use to
upload/download files.  However, the possible problem arises that several
people may be trying to upload/download files on this port at the same time.
So, I'm thinking of implementing a queue to test for the availability of the
port and process each clients request in turn.

Does this make sense?  I thought of making available several ports for this
purpose, and if one isn't available, use another that is. But this occurred
to me if I went this route.  What if the server app is behind a firewall and
we want to limit the number of available ports for security reasons.  Having
many holes in the firewall would be potentially dangerous. This is why I'm
thinking it best to stick with just the one port for uploading/downloading
files.

What do you think?

Alan


"John McGrath [TeamB]" <ng-b@JPMcGrath.net> wrote in message
news:xn0dpgfdz8cuc30009@newsgroups.borland.com...
> On 11/6/2004 at 3:28:19 PM, Alan Shiers wrote:
>
> > i.e. ServerSocket socket = new ServerSocket(2500);
> >
> > Let's assume this port is already being used by another thread.
> > Is there some way to check if the port is already active so that
> > we can allocate a different port number or at least continue to
> > check the port until it becomes free?
>
> The constructor will throw an exception if the port is in use.
>
> -- 
> Regards,
>
> John McGrath [TeamB]
>
> ---------------------------------------------------
> Before sending me e-mail, please read:
>     http://www.JPMcGrath.net/newsgroups/e-mail.html