It just goes nuts under most circumstances. You'll eventually reach a connection limit imposed via the Player (or the browser), and making new requests will either queue up inside HTTPRequest, or fail instantly. Not sure which off the top of my head :) We've had problems when trying to load too many WSDLs at once (in flex 2 admittedly), so we simply queue them now.
In most circumstances where a SOAP request is triggered by a user event (rather than a background poll), I disable the control in question until a result arrives. Perhaps "until a result arrives" isn't what you need, but there's probably a similar solution. -Josh On Thu, Jun 26, 2008 at 2:45 PM, Alex Harui <[EMAIL PROTECTED]> wrote: > Not sure, but I'd guess it keeps making server requests. > > > ------------------------------ > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *fumeng5 > *Sent:* Wednesday, June 25, 2008 12:35 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] Event overloads and the Flex framework > > > > Hi, > > After a long build we're testing and noticing a lot of time out errors > and other things from remote calls to our Java services. One question > that has been posed to me that I don't know how to answer is this: how > does Flex handle someone clicking madly on a button that invokes a > remote service? For example, is there a 1:1 ratio in the sense that > for each call made there will be a response...eventually, or is there > some threshold where Flex will queue the calls or cancel all pending > calls and only return the last one? > > Just trying to wrap my head around this. If anyone has some experience > with this I'd love to hear. > > Thank you, > > Fumeng. > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
