Jarosław, You should check out the MAX session on Adobe TV to see what they are thinking. Right now, there would NOT be any shared memory space between the two (similar to AIR Native Extensions), however, you can send copies of variables between a child worker and a parent (in their terminology, a "promise").
This is there to help reduce race conditions and other nasties that come from inexperienced programmers dealing with multiple threads. -Nick On Mon, Feb 6, 2012 at 2:46 AM, Jarosław Szczepankiewicz < jszczepankiew...@gmail.com> wrote: > it will materialize for sure (the question is when) if they want to > "invest in gaming", currently even low end machines have at least two > physical cores. But I am afraid that the api given to the user will be > not comparable to what we call worker i.e. in java. I speculate but in > order to not complicate AVM internal synchronization they probably > will use workers in form something of swfloader (from flex). Separate > swf with passed variables (by values), without access to some shared > memory (stage, display list, arrays etc.), returning some new > objects?. Something more comparable to modern languages with > multhtreading will complicate the internals of AVM, and adobe can not > afford making the AVM not backward compatible at this moment. But that > only my speculations. > > 2012/2/6 Nicholas Kwiatkowski <nicho...@spoon.as>: > > Multithreading (actually, it is a psudo-thread using child workers) was > > talked about publicly at MAX a few months ago. They have not committed > to > > anything, but they did state that they have it on their current roadmap. > > To us, that means that we may see it in a future release of the FP > > (hopefully sooner than later), but it may never materialize. > > > > -Nick > > > > On Sun, Feb 5, 2012 at 5:04 PM, Stephane Beladaci < > > adobeflexengin...@gmail.com> wrote: > > > >> Agreed, I do not believe we need Flash Player to be opened source to do > >> great stuff with Apache Flex, as I think you mentioned before Alex the > cost > >> for Flex is now 0 since the community will be developing so even with > the > >> Flash Player as it is we should be able to keep pushing Flex further > than > >> Adobe did since there is no commercial agenda anymore. Adobe will > probably > >> also improved the Flash Player as part of their own agenda and use, is > >> multi threading still on the map for this year? > >> > >> > On 2/4/12 5:24 PM, "Stephane Beladaci" <adobeflexengin...@gmail.com> > >> wrote: > >> > OK, that's enough speculation for now. Let's move on. I will > probably > >> ask > >> > my management chain every year on the anniversary of Apache Flex's > >> > acceptance into the incubator if this is the year we will open source > it. > >> > Last time I asked, the answer was not "never". > >> > > >> > But for now, this podling has to assume there won't be any > improvements > >> in > >> > the flash player and make the best of what we have now. And I am > still > >> > convinced that what we have now is capable of really impressive stuff. > >> > > >> > -- > >> > Alex Harui > >> > Flex SDK Team > >> > Adobe Systems, Inc. > >> > http://blogs.adobe.com/aharui > >> > > >> >
