As the title suggests, why are the applyResult and applyFault methods of AsyncToken marked mx_internal?
There have been a few times that I would have liked to use AsyncToken in my code, but I've ended up re-writing it because I don't want to force clients to use namespace mx_internal.
Well, as stated somewhere in the livedocs (I think)
mx_internalis used to mark things in the framework that might change over time (apparently they thought C# and Java are doing it wrong with the deprecated stuff). As to the exact reason why those particular methods are markedmx_internalonly the developer that marked them knows. They probably met one day to discuss it and it went something like: "Hey. What access do we want for those methods" "I don't know, do we want them to be overridable?" "Not sure" "Ok, let's make themmx_internalthen". There were many cases where methods that should have been marked protected were markedmx_internal(or private which is even worse in some cases) instead, and it's one of the most annoying things in the flex framework.Also, you're using the
mx_internalnamespace whether you want it or not, because most of the components in the framework import it, so if you use the flex framework components, your build already includes it.