[Lazarus] FCL-web and bandwidth usage

[michael.vancanneyt at wisa.be]

On Tue, 27 Mar 2012, Graeme Geldenhuys wrote:

> Hi,
>
> This is probably one of the big reasons I dislike (hate is a bit
> harsh) the current state of the internet - it's all a bandwidth hog
> forcing everything to be slow. And seeing that just about every second
> website is a near "web application" makes the matter even worse.
>
> Here is a breakdown of bandwidth used loading various websites (one
> web page only). The results are rather alarming!! In every case the
> actual document content is a fraction of the total bandwidth.
> JavaScript (most popular in this sample being jQuery) being the
> biggest bandwidth hog.
>
> So next time, don't just blindly throw in various JavaScript
> frameworks to make your web app or website look good. Think about the
> bandwidth being used per loaded page too. Optimising and reducing the
> amount of JavaScript will clearly improve the loading time and
> responsiveness of you website.
>
>
>  http://mike.teczno.com/notes/bandwidth.html
>
>
> So has anybody done some bandwidth breakdowns of there FCL-web based
> websites or web applications? How do you fare?

FCL-Web by itself does not create bandwidth hogs. It does not tell you what
to send to the browser. So All depends on what you do with fcl-web.

Javascript is not something you can avoid. People have come to expect a
certain functionality from a website, which can only be delivered with
Javasvript. If you don't provide it, your product will not sell. 
It's as simple as that.

That said, Javascript is not all bad; 
Depending on what you do, it can actually save you a lot of bandwidth by
saving complete page reloads.

Michael.