The module SWFs load asynchronously and will not affect interaction.  What
will affect interaction is how many display objects are in each module's
screen.  So preloading modules may not solve your problem.  Make sure you
are using creationPolicy correctly.

On 8/13/13 11:23 PM, "Raj U. Shaikh" <raj.sha...@mastek.com> wrote:

>Thanks Om,
>But in that case if I satrted loading these bunch of modules through
>urlrequests it will halt screen and user will not able to interact with
>screens.
>Isnt it?
>
>-----Original Message-----
>From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
>Muppirala
>Sent: Wednesday, August 14, 2013 11:20 AM
>To: users@flex.apache.org
>Subject: Re: Caching Modules in background
>
>One simple way would be to just make a bunch of urlrequests and let it
>download and get cached by the browser.
>
>When it is time to actually load the module, load it again with the same
>url - this time the swf loads from the cache and will be much faster.
>Loading from the disk would make the module available in the next frame
>itself.
>
>Hope this helps.
>
>Thanks,
>Om
>On Aug 13, 2013 10:35 PM, "Raj U. Shaikh" <raj.sha...@mastek.com> wrote:
>
>> Hi,
>> Is there any way to cache/load modules (in background).
>>
>> We have a big application which is divided in different modules. There
>>are
>> some screens where around 10+ modules are loaded in different parts of
>> screen.
>> My problem is that when user comes to these screen screens get locked
>>for
>> around 8 to 10 seconds to load these modules. I am able to identify
>>these
>> (n) number of modules in front of user click it.
>> How to load these modules in background? Without locking screen(so user
>> can interact with screen)?
>>
>> (Using flex 4.1)
>>
>>
>>
>> Thanks & Regards,
>> Raj Shaikh
>>
>> MASTEK LTD.
>> In the US, we're called MAJESCOMASTEK
>>
>>
>> 
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Opinions expressed in this e-mail are those of the individual and not
>>that
>> of Mastek Limited, unless specifically indicated to that effect. Mastek
>> Limited does not accept any responsibility or liability for it. This
>>e-mail
>> and attachments (if any) transmitted with it are confidential and/or
>> privileged and solely for the use of the intended person or entity to
>>which
>> it is addressed. Any review, re-transmission, dissemination or other
>>use of
>> or taking of any action in reliance upon this information by persons or
>> entities other than the intended recipient is prohibited. This e-mail
>>and
>> its attachments have been scanned for the presence of computer viruses.
>>It
>> is the responsibility of the recipient to run the virus check on e-mails
>> and attachments before opening them. If you have received this e-mail in
>> error, kindly delete this e-mail from desktop and server.
>>
>> 
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>MASTEK LTD.
>In the US, we're called MAJESCOMASTEK
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Opinions expressed in this e-mail are those of the individual and not
>that of Mastek Limited, unless specifically indicated to that effect.
>Mastek Limited does not accept any responsibility or liability for it.
>This e-mail and attachments (if any) transmitted with it are confidential
>and/or privileged and solely for the use of the intended person or entity
>to which it is addressed. Any review, re-transmission, dissemination or
>other use of or taking of any action in reliance upon this information by
>persons or entities other than the intended recipient is prohibited. This
>e-mail and its attachments have been scanned for the presence of computer
>viruses. It is the responsibility of the recipient to run the virus check
>on e-mails and attachments before opening them. If you have received this
>e-mail in error, kindly delete this e-mail from desktop and server.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>

Reply via email to