HTML5 and Page Size reduction - My Perspective

AT&T network serving 16 petabytes of Data each day http://en.wikipedia.org/wiki/Petabyte
This is not 100% HTML content it includes video/audio other media type content. I found based on html5 new tags, the size of the page can be reduce upto 50% of the total mark up size. What it means is using concise tags eliminate unnecessary markup like extra html tags and CSS and otherstuffs. And also two important media tags Video and Audio would reduce plugin code (it may be one time + some other extra stuffs) It would be huge boon to network. Websocket will enable easy push feature and binary data transfer which also will play friendly to payload. So ultimately new version html (html5) will need less mark up to achieve same effect and also some time less extra enabler code. Size reduction is mainly due to as I said above, Since reduction in html code to achieve same look and feel will ease the Search engine parsing -- it also saves power cost and hence environmental friendly --- connecting loose ends. One more side effect would be performance improvement on the browser as browser needs to parse, understand and apply style etc to only few elements.

1. New html tags so less mark up
   
2. New media tag - video and audio so less dependency need for using media
3. Websocket -- duplex communication eliminates unnecessary round trip and concise data transfer
   
4. Improved browser performance
   
5. Search engine friendly -- less markup to parse and no proprietary plugin to understand
   
6. Less power usage - markup generation and Search engine content parsing
   

Erlang - Fileupload

I have been playing with ewgi --- wsgi equivalent of Python. It is spec which is above and top of particular application server likes (YAWS or Mochiweb or inets or misultin) so the application developed for ewgi can run on any server without any modification, ideally.
I have been playing with mochiweb and couchdb and using beepbeep as my application framework. Beepbeep has integration with ewgi and so for good for simple usecase. But I was not able to do file uploading. I added missing fileupload piece to beepbeep but theoretically it should work for any application running on EWGI and Mochiweb. So I forked beepbeep and added my file upload module, you can get it from here http://github.com/sendtopms/beepbeep/tree/master