顯示具有 Web Application Research 標籤的文章。 顯示所有文章
顯示具有 Web Application Research 標籤的文章。 顯示所有文章

2009年11月24日 星期二

News - SPDY

After Google Frame, SPDY has been published as a replacement to HTTP protocol to speed 2x page loading on the web.

To try to speed up the web, Google provides solutions not only from browsers(Application Layer), but from Session and Presentation Layers, SPDY.

1. Google Frame : can plug into IE.
2. Google Gears : offline Ajax.
3. Google Chrome : web browser.
4. Google SPDY : protocol.

Speed, Simplicity and Security...

2009年11月19日 星期四

Book Review : Web Application Architecture

Web Application Architecture - Principles, Protocols and Practices (Leon Shklar and Richard Rosen)

This book introduces web application from initial protocols, down layers to up layers. I think it will be a good book to new developer to view the entire architecture of web applications.



2009年11月18日 星期三

MSDN View To Web Application

What is web application?
Let's take reference of MSDN.

The view it held from the structure of Client-Server architecture. Server is responsible for data process, response clients requests by tagged data (xml, for example). Client uses the response tagged data to render or change the status of local application to represent result of the requests to user.

Architecture Research



















Before digging myself into the world of web application, or if you like this fashion "cloud computing", I would like to draw what is the "World" it will be in my mind.

Q: Will it involve protocol stuff?
A: Yes, Google introduces "SPDY" and claim 2x faster web in design.

Q: Will it just communication between servers and devices?
A: No, I think the form of communication will not only servers-and-clients but peers-to-peers. About this, I will put Google APIs on my research list.

Architecture of Web Application

There are some fundamental techs to construct a web application.
But before that research, what is so-called 'web application'.

My idea is that :

The kernel value of a web application is to integrate online and offline users, and communicate between clients and servers. So that, there is no limitation to which device that users would like to take: laptops, desktops, cellphones, cars, etc. And also, there is no limitation to which operation systems and browsers that users use it by their own habits: Windows, Linux, Chrome OS, IE, Firefox, etc.

If I think "Hey, just rewrite your own code by JavaScript and PHP....", I was so wrong in this topic. OK! obviously, if Google provide a "web office" for free, it will be a big hit to Microsoft. "Free Word and Excel!" ... Can you image?

"No installation, no need to upgrade" is not enough to attract people to move their feet to your circle, so does "Free".

"Google docs", a good example here, provides some basic document functions to online edit. It also gives chance to invite people to edit the content as a group of co-worker. There will be many web applications that I can image them mostly from the traditional applications we used will be "migrated" to web based application with this kernel value - Groupy!

Let's integrate it:
A web application will put these concepts together
a.) online and offline usage. (asynchronization and synchronization)
b.) client and server.
c.) peer to peer.

A web application may have these functions
a.) groupy
b.) broadcasting



First Paragraph

These are the principles of my blog here.
Firstly, I would like to introduce some new techs from Google, yes, cloud computing technology, to be my daily research to rich my career and interests. Also, I like my blog to be my private place, even it is some kind of 'impossibility'.