Kelly, valid point and I've already spent considerable time optimizing things to reduce the size and improve the response time of individual requests. Pagination is only one of the scenarios. There are situations such as during application start up where routine requests can take longer than you think they should.
Bottom line, however, it is the decision of the developer to have longer requests or not, and this should not be pre-determined for them by the framework - that's why you have the requestTimeout parameter in the first place. It works as expected on the Mac, just not on Windows. ________________________________ From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Kelly Sent: Wednesday, August 11, 2010 1:55 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Vote For This Critiical RemoteObject bug Why do you have RemoteObject calls that normally take longer then 30 seconds to complete? Why not just make multiple requests? I would question calls that average more then 300ms for small data and 3s for larger data. Any data loads larger then that should be paged. Any logic that takes longer then that should run in background and periodically poll for updates. On 08/11/2010 08:03 AM, Battershall, Jeff wrote: Somehow a critical bug has fallen through the cracks - essentially RemoteObjects in AIR/Windows timeout after 30 seconds no matter what value you have set in requestTimeout or URLRequestDefaults.idleTimeout: https://bugs.adobe.com/jira/browse/FP-4934 There seems to be some question as to whether it is an SDK bug or an AIR bug, but regardless, it is affecting production systems and needs to be resolved ASAP. I'm hoping we can get the issue escalated. Voting for it should help increase its visibility. Jeff Battershall Application Architect Dow Jones Indexes jeff.battersh...@dowjones.com (609) 520-5637 (p) (484) 477-9900 (c)
