It's quite likely than I am misunderstanding or at least not completely understanding the problem. Can you be more specific in the BORKness of my network setup? From Walden's reply it sounds like the custom application is using ports in the "ephemeral" range. Maybe it's best to change that application to not use ports in that range? Is that what you mean by BORKED?
Is BORKED a Swedish aphorism? It reminds me of the Swedish chef from the muppets. Thanks! Ted On Oct 10, 8: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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
