Skip to main content

Ajax World East 2008 - Day 1 Report

Posted by arungupta on March 18, 2008 at 7:03 PM PDT

Ajax World East 2008
started earlier today.

I delievered my "Web 2.0 Application development using jMaki" and the
slides are available href="">here.
There were several demos shown in the talk (using href="">NetBeans and href="">GlassFish)
and they are all accessible at the links mentiond below:

  • href="">RSS
    feeds in jMaki widgets
  • href="">Mashing
    up the Maps
  • href="">Rails
    powered by jMaki
  • href="">Sun
    Tech Days Event Map

Several other related demos are available href="">here.
Luckily I could deliver without much hassle inspite of having a high
fever and cough! I hope I can hold at least until tomorrow morning when
the href="">big
preso is scheduled @ 11:35am.

Anyway I attended 3 more talks today and took notes to share:

  • href="">Picking
    the Right Technology for Enterprise Rich Internet Applications
  • href="">Performance
    Tuning your Ajax Applications
  • href="">Performance
    Paradigm of a Mashup World

See below for notes from each talk.

The first talk I attended was: href="">Picking
the Right Technology for Enterprise Rich Internet Applications.
I got little late and the session was packed with attendees standing
way outside the room so I joined them.

The session talked about  href="">AIR, href="">Silverlight
& JavaFX
as three possible technologies for Enterprise RIA. Per the talk, here
are the basic criteria for RIA tools requirement:

  • Seamless deployment on client
  • High penetration of runtime
  • Web browser independence
  • Fast client/server communication protocol
  • Robust security

Of course, this session was given in Ajax World so pros/cons of Ajax
were dicussed:

width="50%">Pros of Ajax width="50%">Cons of Ajax
No deployment
Ajax apps are
browser depdendent
100+ Frameworks 100+ Frameworks
Open Source, no
need to purchase
software license
Expensive due to
long cycle, skilled
developers demand
top rate
JavaScript is an
language, entire source
code can be viewed using "View Source"
communication speed is not
optimizedf for Ajax

And then basically it talked about the three technologies and their
pros & cons are well captured in the slides.

The second session I attended was href="">Performance
Tuning your Ajax Applications. This was an interesting
session and I learned a few tricks. Interstingly we have implemented
quite a few of these performance enhancements in href="">jMaki already.

Improving the performance of Ajax
applications require tuning the
following parameters:

  • Number of requests
    • Reduce number of JavaScript files that are loaded. This
      is the most important since each request to the
      backend adds extra cost. Even when the scripts are cached, the browser
      still makes a request (unless Since-Modified header is set correctly).
    • Typical approaches are to concatenate the files at dev
      time or at runtime based upon request.
    • Dev time approaches
      • Ant - concat all JS files using <concat>
      • Dojo - Run Rhino over all provide/requires and then
        the files
      • Command-line
    • Run time approaches - Concatenation happens depending
      upon the request. Cons are:
      • Server-side dependent
      • Makes it harder to distribute code
      • Server is loaded as concatenation happens on server
        (mitigated with caching)
      • Works for <15 JS files
      • Does not track dependency
  • Size of requests
    • Remove white spaces and comments (Packer, Dojo,
      YCompresser, SafeCompress, ShrinkSafe are some of the tools)
    • Shorten the variable names
    • Gzip the code
    • Semicolon is optional but needed if you remove EOL
      (careful when compressing the code)
      • Drastically reduces the file size (e.g. Apache XAP
        reduced the file size from 330 kb to 70 kb)
      • Lots of gzip tools
      • Need to put appropriate headers so that browsers
        recognize gzipped content
    • Coding Style
      • Single line "if" and "for" do not need "{ }"
      • Combine var declarations into a single var such as var
        x=1, y = 2;
      • Use JavaScript style object
  • Time of requests
  • Time of initial code completion
    • Minimize the time that is executed @ start up
    • Bring the data once the initial page is loaded
    • Show images telling users that something is going on
      • Distracts user from the time it's taking
  • Other tips
    • Don't write your own parser  - use the native
    • "If" statement optimization
    • Use the native facilities like getElementById() or
    • Consider different approaches of DOM creation
      • Tail Recursion
      • Setting the value in innerHTML
    • Consider JSON over DOM for object graph traversal - JSON
      could be much faster

Similar tips can be used for CSS as well.

My third talk of the day was href="">Performance
Paradigm of a Mashup World.

This talk given by Vice President of href="">Webmetrics and laid
a special emphasis on "Collaborative Monitoring" for performance
measuring any mashup. This process involves not only monitoring your
own application, but also setting up agents that measure performance
with other services being invoked in the mashup, their further partners
and so on. It also talked about a layered approach of using:

  • Standard monitoring - HTML page load time, DNS request
    processing time, etc.
  • Pixel Mapping monitoring - required mainly for GUI
    intensive application
  • Web services monitoring - Used for partner monitoring

This was further clarified using a 6-step process:

  • Know your apps
  • Learn where the points are in your ecosystem
  • Measure your perspective
  • Monitor your APIs
  • Collaborate within your organization
  • Collaborate with your partners & customers

That's it!

Check out some of the pictures:

style="width: 216px; height: 288px;" alt=""

The expo hall opens tomorrow and Sun's booth is right between the
ballroom and the main door to expo hall, can't miss us ;)

The complete album is available at:

height="192" width="288">

Internet connection at the Roosevelt
is painfully slow inspite of
charging $14.95/night where as most of the "modern" hotels offer free
wireless :(

Technorati: conf
ria href="">sun href="">web2.0

Related Topics >>