All of those button click - server requests are queued up till the end
of the frame. The Flex/Flash will send them out. I'm not sure about
simple http. But, If you are using the Blaze/LCDS servers, flex actually
sends them all as a set. Basically the servlet will get an Array of
requests. It will
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
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
: [flexcoders] Event overloads and the Flex framework
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
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] wrote:
There
: [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
6 matches
Mail list logo
