I'm not saying there is a per-frame connection limit that is different from the total connection limit of the player/browser. However, I think I've read that requests in a frame are queued to the end of the frame, which would make it easier to hit that limit with code, but users probably aren't fast enough.
However, I'm so far out of my area, it is time for me to bail on this thread. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, June 25, 2008 10:12 PM To: [email protected] Subject: Re: [flexcoders] Event overloads and the Flex framework I never thought there'd be a per-frame request limit different from the "number of open http sockets" limit. Probably easy enough to verify had I a spare half hour, but I'm used to queuing things now anyway :) -Josh On Thu, Jun 26, 2008 at 2:59 PM, Alex Harui <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: There probably is a connection limit, so if you try to get to too many places at once in a single frame, you can have problems. But I understood the question to be about the user hitting a button fast which I would assume hits the same request, and at user speed which is usually slower than the frame rate so the requests shouldn't get queued. However, I'm way outside my area of knowledge. -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
