When deploying a flex app as a precompiled swf file, the flex jsp tag
<mm:flash source="foo.swf"/> appears to generate the same code as the
Flex html wrapper as described in livedocs. 

However, it is not clear what sort of Flash player version detection
this does versus the detection which is performaned when one uses the
<mm:mxml source="foo.mxml"/> tag.  The livedocs imply that there is a
bit more going on with version detection than you can see by simply
viewing the source of the resulting html page.

Does anyone know what sort of flash player detection is and isn't
handled by the flash tag versus the mxml tag?

Does anyone know what is meant by this statement in Livedocs: "When
using the Flex JSP Tag Library to define a Flex application, Flex does
not include the complete Flash Player detection scheme. However, the
<object> and <embed> tags do include minimum version information and
download locations."

And finally, when I load an mxml file directly via http://foo.xml,
flex appears to do extra version testing optimizations (referred to in
the LiveDocs under "Optimizing version detection").  When we use the
mxml or jsp wrappers, does flex use these optimzations under the
scenes?  If not, does anyone know if these optimizations affect the
client alone or the client and the server?

Thank you!




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to