3 ms·
True, but unfortunately adobe is stuck using AS3 on their VM; silverlight gets to leverage all the .net work. Hopefully they'll add threads to flash sometime i
by dantheman 18y ago
True, but unfortunately adobe is stuck using AS3 on their VM; silverlight gets to leverage all the .net work.
Hopefully they'll add threads to flash sometime in the future, that is the most limiting factor facing it today.
- TJensen 18y agoI cringe to think what the developers at my work would do with threads in the Flash VM. I'd just as soon keep a single-threaded model.
- dantheman 18y agoThe single thread model has some serious limitations. For instance maybe you would like to load some images & then popup a component containing them. In a threaded world, you can have synchronous communication where it just waits till the download is complete before loading what depends on it. Right now you have to register callbacks, sure that's not too tough, but chaining like that makes it more difficult than it should be. download -> componentA > componentB > ComponentC whereas it might be easier to just go: CompnentA(file.download()); instead of file.Download (CompACallback, FaultCallback);