As far as I know, every OS out there has a primitives, available to programs through a socket library, which choose the "ephemeral" port for the client side of the binding when a client opens a TCP connection, cycling through the high range of numbers designated for that on each new connection request. It is unlikely that your browser is getting one of the low reserved numbers for its binding. More likely is that one of your custom applications has "reserved" something in the ephemeral range. That can work ok, as long as your custom application starts early enough to get its port bound before it's given out for some other purpose.
Walden On Oct 10, 9:41 am, Reinier Zwitserloot <[EMAIL PROTECTED]> wrote: > The browser controls that (obviously). > > Your network setup is completely, utterly, -BORKED-, if this is > causing problems. That means any connection made by the browser, for > any reason, could randomly fail. I'm guessing you're misunderstanding > the problem. > > On Oct 10, 2:54 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > > > Is it possible to limit the outbound port range for making > > XMLHttpRequets? We are running into issues were the client app is > > starting to use some ports that are "reserved" by some other custom > > applications. When a request is made to a server on port 80 / 443, > > what determines the client side port that is opened for that > > communication? Is it controlled by GWT, IE / Firefox, etc, OS? > > > I am using GWT 1.5 and IE 6 on windows xp if it makes any difference. > > > Thanks! > > > Ted- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
