On 7/26/05, jamiebadman <[EMAIL PROTECTED]> wrote: > I have a deep-down feeling I might be asking a stupid question here - > but I was once told there are NO stupid questions - yeah, right!
As a wise code-mentor once said to me: There aren't stupid questions, only people who are too stupid to ask. So yes, it was a stupid question (joke). > If this is *not* possible, could someone explain to me the > advantages of Flex as a server-side system ? Yes, but not the way you think it will probably come together. There are two main ingredients that you will probably need to research some more in order to make a better informed decision to suite your objective(s), they are mx:Loader and Runtime Shared Libraries (RSL). You can *kind* of piece together an application per user through these concepts, especially leveridging XML - the key to do this though, is much the same way you would bake a cake - you need the ingredients into the mix in order to bake it, the icing can be loaded after but thats a module that can be seperate (based on a users preference). Sorry if the analogy is weak but its after a 13hr code-off..so bare with me. What i'm trying to say is that if you plan on using a mx:Button in your application, and your first stage of the SWF doesn't have that at runtime, but want it to be used based on a remoting call's result...then you're going to have to load that in via the initial first stage - or - unless you load in a swf which embeds the symbol, and *then* you can use it (second stage) *pant*.. (i'm too afraid to re-read that hehe). In theory (i've never backed this up btw, its all based on reading and theories) you can piece together an application piece by piece, but you have to plan your staging up front and kind of pinpoint when user(s) will need components, then using the RSL concept they can bring in such components as needed. There are a few things to be aware of (ie pulled from docs) # The aggregate size of the RSL plus the Flex application will be larger than a Flex application that internalizes all of its assets. However, file size across multiple applications will be smaller. # The client must make additional HTTP requests to get the RSLs used by a Flex application. This can add latency to the application startup process. Typically, the number of RSLs is not great, so the number of requests is not great, either. # The compilation of a runtime RSL can add additional application startup time because a separate compiler instance must be created on the server. This adds latency to the first request only, since subsequent requests will request the existing RSL without the need to recompile it. Again, easist solution would be use CFMX to pre-roll your MXML...but nothing wrong with a bit of a good challenge to ear ones pay ;) hehe. Hope that helps, if you need a flex-gun-slinger to do the above for you, i'm cheap ;) hehehe.. -- Regards, Scott Barnes http://www.mossyblog.com -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 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/
