I suppose this is an answer to the OP question, but it does not seem so to
me.
When workers were introduced/tested/released, I went through the Beta cycle
and subsequently devoloped multi-worker AIR applications layering the AIR
SDK atop the last available Flex SDK from Adobe.
In the time since, I, like I presume most, have been waiting to see whether
or not we can get back to that state of affairs using the Apache Flex SDK
with the most current AIR SDK layered from Adobe. Our current understanding
is that yes, we can 'sort of try it', but because the new AAC2 Compiler
cannot handle our Spark Componentry when injected via MXML, we really are
not yet back to square one. As far as I can tell, the same ambiguity now
exists with regards to Workers.
Can someone post an official, unambiguous answer to where these key
capabilities stand?
It is painfully clear that the Gaming Product Manager for all things
Actionscript is doing his best to distance his team's efforts from those of
the Flex community. The Spoon folks wanted this challenge; will the Spoon
and/or Adobe folks please stand up and give us their answer to where things
stand especially since the release of the last, verbose, unhelpful Statement
of Direction from Adobe since the killing off of ActionScript Next.
----- Original Message -----
From: "Justin Mclean" <[email protected]>
To: <[email protected]>
Sent: February 18, 2013 06:07 PM
Subject: Re: Worker/Mutex/Condition
Hi,
Our applications run with Flex 4.6, we're considering upgrading to 4.7 for
the concurrency features.
The concurrency features are part of the Flash Player (first added in 11.4)
not the Adobe Flex SDK. The Adobe Flex SDK does support flash player 11.4
and does compile against 11.5 and 11.6 but hasn't been fully tested with
those versions.
Thanks,
Justin
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2899 / Virus Database: 2639/6110 - Release Date: 02/17/13
