Re: [flexcoders] RE: Vote For This Critiical RemoteObject bug
I noticed it was filed against the player. I assumed you’d essentially proved it was an AIR issue. If so, there is no source to look at or patch. If the same requested timeout works on Mac or in Flash, it probably is an AIR/Windows issue. They generally like non-Flex test cases so if you can conjure up a simple AS-only case with NetConnection and show that timeouts are not working, that might expedite things. RemoteObject lives on top of NetConnection. On 8/12/10 10:00 AM, Battershall, Jeff jeff.battersh...@djindexes.com wrote: Alex, Can you put me in touch with someone on the SDK team re: this timeout issue? I’ve started to dig through the Flex SDK source but have not run across the smoking gun yet – a lot of the Remoting related classes haven’t been modified since 2009. Seems to me that if I knew the correct place to look, devising a patch could be relatively straightforward. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Battershall, Jeff Sent: Wednesday, August 11, 2010 11:03 AM To: 'flexcoders@yahoogroups.com' Subject: [flexcoders] Vote For This Critiical RemoteObject bug 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) -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
RE: [flexcoders] RE: Vote For This Critiical RemoteObject bug
Alex, I've been in touch with Chris Thilgen, from the AIR team who tells me it's a Flex SDK issue. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Thursday, August 12, 2010 2:42 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] RE: Vote For This Critiical RemoteObject bug I noticed it was filed against the player. I assumed you'd essentially proved it was an AIR issue. If so, there is no source to look at or patch. If the same requested timeout works on Mac or in Flash, it probably is an AIR/Windows issue. They generally like non-Flex test cases so if you can conjure up a simple AS-only case with NetConnection and show that timeouts are not working, that might expedite things. RemoteObject lives on top of NetConnection. On 8/12/10 10:00 AM, Battershall, Jeff jeff.battersh...@djindexes.com wrote: Alex, Can you put me in touch with someone on the SDK team re: this timeout issue? I've started to dig through the Flex SDK source but have not run across the smoking gun yet - a lot of the Remoting related classes haven't been modified since 2009. Seems to me that if I knew the correct place to look, devising a patch could be relatively straightforward. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Battershall, Jeff Sent: Wednesday, August 11, 2010 11:03 AM To: 'flexcoders@yahoogroups.comflexcoders@yahoogroups.com' Subject: [flexcoders] Vote For This Critiical RemoteObject bug 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) -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
Re: [flexcoders] RE: Vote For This Critiical RemoteObject bug
It could be, although it is rare for Flex to have something work on Mac but not on Windows. The runtime teams usually point the finger at Flex hoping that it is us because it is hard for them to debug Flex test cases since they are large and complex. It is a better to start with us anyway if there is any doubt. We do our investigation and generally create simpler non-Flex test cases if it turns out to be a player issue. If you think Chris is right, file the bug again against the Flex project. Do you have a support contract with Adobe? If so you should escalate via that route. I think you can also just contact support anyway. If you have hooks into Adobe in a similar fashion (Adobe Sales, Adobe Consulting), use them to file a support case on your behalf. If it gets enough votes, our QA will probably notice. Next release isn’t until 2011 and lock down isn’t until end of year probably so there is still time, but if you need resolution now, Adobe Support is the way to go. If any of your executives know the phone # of an Adobe executive, that works too, but it doesn’t make me happy when sh__ rains down that way. The RemoteObject code has not changed much lately. I don’t now it that well but eventually everything boils down to NetConnection. I think there is a NetConnectionChannel class in there. We’re in a busy period for a few weeks otherwise I’d just look now. A support escalation will allow someone to official stop and look. On 8/12/10 12:06 PM, Battershall, Jeff jeff.battersh...@djindexes.com wrote: Alex, I’ve been in touch with Chris Thilgen, from the AIR team who tells me it’s a Flex SDK issue. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Alex Harui Sent: Thursday, August 12, 2010 2:42 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] RE: Vote For This Critiical RemoteObject bug I noticed it was filed against the player. I assumed you’d essentially proved it was an AIR issue. If so, there is no source to look at or patch. If the same requested timeout works on Mac or in Flash, it probably is an AIR/Windows issue. They generally like non-Flex test cases so if you can conjure up a simple AS-only case with NetConnection and show that timeouts are not working, that might expedite things. RemoteObject lives on top of NetConnection. On 8/12/10 10:00 AM, Battershall, Jeff jeff.battersh...@djindexes.com wrote: Alex, Can you put me in touch with someone on the SDK team re: this timeout issue? I’ve started to dig through the Flex SDK source but have not run across the smoking gun yet – a lot of the Remoting related classes haven’t been modified since 2009. Seems to me that if I knew the correct place to look, devising a patch could be relatively straightforward. Jeff From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Battershall, Jeff Sent: Wednesday, August 11, 2010 11:03 AM To: 'flexcoders@yahoogroups.com flexcoders@yahoogroups.com ' Subject: [flexcoders] Vote For This Critiical RemoteObject bug 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) -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
