Despite the advantages of centralized hosting of SWZ files, in that it speeds
initial load times for Flex applications after the first load, I have an issue
with centralized SWZ files under the Adobe model, in that it exposes an inherent
security weakness: if the centralized cerver hosting the Flex SWZ files ever
crashes, every Flex SWF in the entire internet using SWZ caching ceases to
function. You can build redundancy failovers, but that is still vulnerable to
DoS attacks.

Which is why, despite the sacrifice in efficiency, the decentralized Apache SWZ
model makes a lot more sense: individual companies host their own SWZ files for
their own applications, so that if a DoS or similar attack prevents a Flex app
from accessing the SWZ, only that company's Flex apps are affected, not the
entire internet's-worth of Flex apps which use SWZ loading.


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Sean Thayne wrote:
> Hey Justin,
> 
> Am I wrong that Apache versions of Flex do not have SWZs, they only have
> RSL SWFs, correct?
> 
> Back with Adobe Flex, SWZs allowed the app to take a while to load on the
> first run, but afterwards they cached, so the next open would run very
> quick. Also it didn't matter what site they originally accessed. If they
> went to Yahoo.com and used a flex app there, and then came to my site to
> use a flex app. The RSLs wouldn't need to redownload. As long as they were
> the same version #.
> 
> Thanks!
> 
> ~Sean
> 
> <http://www.skyseek.com>
> class *Sean_Thayne*
>     extends Developer {
>         public $skype = "sthayne23";
>         public $gTalk = "s...@skyseek.com";
>         public $url   = "www.skyseek.com";
> }
> 
> 
> On Fri, Jan 24, 2014 at 2:42 PM, Justin Mclean <justinmcl...@me.com> wrote:
> 
>> Hi,
>>
>>> I really wish that Apache could use the SWZs.
>> You can use them you just need to host them yourself.
>>
>> Thanks,
>> Justin
>>
> 

Reply via email to