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 then treat them all as individual requests and then return them as a set. Doing this helps with the connection limits and behaves as if you send a lot of individual request.. But this also means if you have 3 calls you make one after the other, and 2 are really quick and 1 is really slow. The 2 quick ones will wait for the slow one so they can all return together. But again that is only if they all get triggered in the same frame.
There is also a concurrency (I think that is the name) attribute on the RemoteObject, where you can set it to ignore duplicate responses and just keep the last one. However the server does get hit for all of them. Hth, --nimer From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of fumeng5 Sent: Wednesday, June 25, 2008 2: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.
