|
|
Posted by SpaceGirl on 10/08/07 18:24
Chaddy2222 wrote:
> On Oct 9, 1:47 am, "Jonathan N. Little" <lws4...@centralva.net> wrote:
>> Travis Newbury wrote:
>>> On Oct 8, 8:41 am, Chaddy2222 <spamlovermailbox-sicur...@yahoo.com.au>
>>> wrote:
>>>> Oh yeah and I would have been able to read the bloody thing.
>>> Zoom.... (Yes I know the zoom feature sucks)
>> Hmmm, apparently the deziner forgot to enable the feature. Sorry Chad
>> you're screwed! You'll be coming back to the site with some youngin with
>> fresh perfect eyes in tow to read off the pages for you, right? Yeah,
>> sure...
>>
>> Not saying there is no use for flash, but dammit it is not better than
>> html for conveying textual content on the web. Whether it better than
>> server-side for organizing and disseminating the content is also
>> debatable since in most cases the end result is neither delivered to
>> displayed on the browser any faster nor as flexible is usability once it
>> gets there! The swf of this sitewww.mortgagenews2.commaybe only 27Kb
>
> That's f***ing jygantic!.
> My XHTML docs with a lot of images would equal about 10KB I reckon.
> </goes and checks>.
> No, actually I have a layout for a photo gallery page with about 10
> thumbnails that ways in at about 2KB!
> now try and do that with your fancy bandwith eating Flash
> applications!
Bet it's not. Given the 1Kb IP overhead for every single HTTP request...
With Flash you get two requests (depending how it is built) - one for
the UI, one for the data. In a regular site, every single image or bit
of loaded content is also generating a huge overhead. On a 1Kb GIF, you
are looking at as much as 1.5Kb worth of data that goes with it that
your browser discards. Another thing; if the page containing the Flash
is refreshed, your browser just sends one request back to the server to
check if the file has updated. Do that with your page, and every single
file is checked against the server... again, even if nothing has changed
a the server, you're looking at stacks of traffic.
This gets even better: Flash supports binary sockets, so you can scrap
all the HTTP traffic as Flash makes a direct connection with the socket
provider at the back end... and then the data gets compressed!
You also have to think about what Flash does inside it's 27Kb (in this
case) - once the initial classes are compiled inside of your SWF, reuse
of that code, extending of the classes etc etc will barely increase the
file size at all. You could double the number of their pages in that
site with virtual no increase in file size. Or add stacks of new
functionality. And so on. Could you do this on your page? No. Every new
page means another load of HTML, GIFs and CSS that has to be sent from
the server eating up all your bandwidth :) Caching helps of course, but
even then you are sending traffic.
So, it's very easy to dis Flash when you really don't understand how it
works. It's nowhere near as straight forwards as you seem to think.
--
x theSpaceGirl (miranda)
http://www.northleithmill.com
-.-
Kammy has a new home: http://www.bitesizedjapan.com
Navigation:
[Reply to this message]
|