The way that sockets work, the client doesn't make a request from a specific
port, it is assigned by the OS. It does make a request to a specific port
(in your case 8091). The browser works the same way, if you try to navigate
to a web page, you are not leaving your machine on port 80, you are making a
request to port 80 on the machine you are requesting information from. The
OS has a pool of ports that it will assign to your end point when you
attempt the request. You are most likely going out on a port above 2500,
but it is really hard to say what it will be. And for the most point which
port you exit your machine is irrelevant, it is the port you are attempting
to connect to that is important (in most cases).
--
Jim Fee
Viking Electronic Services
jfee (at) vikinges (dot) com
[quoted text, click to view] "VegasChandler" <webforumsuser@macromedia.com> wrote in message
news:cv2g0o$e59$1@forums.macromedia.com...
> What exactly do you mean by that last sentence that one never knows the
> port
> the request is made on. Not to act the annoying media agent, but you
> really
> didn't answer my question at all with your response. I know what port the
> server will be trying to return, I need to know the port the request
> leaves
> from. If the request still attempts to always leave from port 80 then
> that
> request will always be blocked because the port is closed. Perhaps I just
> don't know enough about socket communication, but I'm willing to learn all
> this.
>
> Originally posted by: Newsgroup User
> i?ve often connected to a tomcat server on port 8080, never had a problem,
> should work perfectly.
> in your example, the server will deliver on port 8091, you never know the
> port a browser or flash player uses to send the request.
>
>
>
>
