On 2/24/12 12:50 PM, "olegsivo...@gmail.com" <olegsivo...@gmail.com> wrote:
> Ah, so you mean you were recompiling a module SWF and reloading it, while
> the other half was still in debugger? I'm not sure, but I think that the
> policy as to load and unload is per domain... but, that's something I
> really don't know. Is it possible that after unloading a SWF only some
> class definitions would "stuck" in the player? Sounds fishy :)
>
> In other aspects, I didn't mean "no version at all", I'm for "per SWF", so
> if the entire SWF was cached, then you would discover it by looking at the
> version in SWF.
I would like per-class. SWCs can get mixed from all over the place, then
loaded in via a module (and not be blocked by some pre-existing definition).
Have either of you handled time-sensitive escalations from enterprise
customers with code written by folks you don't know? That's been part of my
job and probably will continue to be so, and version stamping the classes
helped me out in a way that per-SWF won't and compile time checking won't.
I will not appreciate making that task harder. I cannot understand the
amount of energy being spent on this low overhead solution. I think we have
much bigger fish to fry.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
