HTML and CSS Reference
In-Depth Information
INCREASED USER EXPECTATIONS
As more users moved to using applications such as Twitter and Facebook, and the user
experiences that they deliver, their perception of what can be expected from a Web application
changed. Although applications had become more dynamic through the use of JavaScript, the
experiences were seldom truly interactive. Facebook, with it's real-time wall (and later other
realtime features) and Twitter with it's activity stream centric user interface, and focus on
conversation, demonstrated how Web applications could be highly engaging.
WEBSOCKETS
Earlier on I stated that previous solutions to let servers instantly push data to Web browsers
were considered "hacks". But this didn't remove the fact that there was a requirement to be
able to do this in a cross-browser and standardised way. Our prayers have finally been
answered with
HTML5
WebSockets
.
WebSockets represent a
stardardized API
and
5
6
protocol
that allows realtime server and client (web browser) two way communication over a
7
single connection. Older solutions could only achieve two-way communication using two
connections so the fact the WebSockets use a single connection is actually a big deal. It can
be a massive resource saving to the server and client, with the latter being particularly
important for mobile devices where battery power is extremely valuable.
HOW ARE REAL-TIME TECHNOLOGIES BEING USED?
Real-time Web technologies are making it possible to build all sorts of engaging functionality,
leading to improved user experiences. Here are a handful of common use cases:
