• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Multiple URLStreams throws errors.

Explorer ,
Nov 15, 2010 Nov 15, 2010

Copy link to clipboard

Copied

I have the following code in my app:

var urls:Vector.<String> = new Vector.<String>(); urls.push('http://mydomain.com/transfer/d5-1.bin'); urls.push('http://mydomain.com/transfer/d5-2.bin'); urls.push('http://mydomain.com/transfer/d5-3.bin'); urls.push('http://mydomain.com/transfer/d5-4.bin'); urls.push('http://mydomain.com/transfer/d5-5.bin'); for each (var url:String in urls) {      var urlStream:URLStream = new URLStream();      var request:URLRequest = new URLRequest(url);      request.useCache = false;      urlStream.load(request);      urlStream.addEventListener(ProgressEvent.PROGRESS, progressHandler);      streams.push(urlStream); }

When I run this from a Flex app, it works as expected (multiple streams load simultaneously).  When I run it from an AIR 2.5 app on Windows 7, I get:

Error #2044: Unhandled IOErrorEvent:. text=Error #2032: Stream Error.

for all but the first stream.  Is this a known bug?  Are we purposefully limited to a single URLStream at a time from AIR?  Am I missing something?

Thanks!

Aaron

TOPICS
Performance issues

Views

883

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Nov 17, 2010 Nov 17, 2010

Hi Aaron,

Thanks for reporting this issue!  I can confirm that I'm also seeing the same results on Windows 7, the Mac appears to be fine.  I'm going to do a bit more researching and I'll add this bug to our database.  I'll post back shortly with an internal bug number.

Thanks,

Chris

Votes

Translate

Translate
Adobe Employee ,
Nov 17, 2010 Nov 17, 2010

Copy link to clipboard

Copied

Hi Aaron,

Thanks for reporting this issue!  I can confirm that I'm also seeing the same results on Windows 7, the Mac appears to be fine.  I'm going to do a bit more researching and I'll add this bug to our database.  I'll post back shortly with an internal bug number.

Thanks,

Chris

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 17, 2010 Nov 17, 2010

Copy link to clipboard

Copied

Thanks for getting back to me and getting it logged.  I'd love to be in the loop on the bug's progress.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 17, 2010 Nov 17, 2010

Copy link to clipboard

Copied

LATEST

This bug is now logged internally as #2759165.  While the status on this is not publicaly accessible, please feel free to contact me directly for updates at ccampbel@adobe.com.

As a temporary workaround, could you try changing your application descriptor to:

<application xmlns="http://ns.adobe.com/air/application/2.0">

I'm assuming you're using AIR 2.5 as I couldn't reproduce the problem with 1.5.3 or 2.0 namespaces.  If so, you might also need to comment out and add the following lines in your app descriptor:

<!-- <versionNumber>1.0.0</versionNumber> -->

<version>1</version>

Thanks,
Chris

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines