RE: [flexcoders] Event overloads and the Flex framework
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.
RE: [flexcoders] Event overloads and the Flex framework
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.
Re: [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 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]
RE: [flexcoders] Event overloads and the Flex framework
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. From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, June 25, 2008 9:56 PM To: flexcoders@yahoogroups.com Subject: Re: [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 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] mailto:[EMAIL PROTECTED] wrote: Not sure, but I'd guess it keeps making server requests. From: flexcoders@yahoogroups.com mailto:flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com mailto:flexcoders@yahoogroups.com ] On Behalf Of fumeng5 Sent: Wednesday, June 25, 2008 12:35 PM To: flexcoders@yahoogroups.com mailto: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] mailto:[EMAIL PROTECTED]
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] 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]
RE: [flexcoders] Event overloads and the Flex framework
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: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, June 25, 2008 10:12 PM To: flexcoders@yahoogroups.com 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]
