Cal Evans

Speaker: Paul Reinheimer
This talk will examine the two greatest problems in Ajax development (except for that pesky browser issue): Exactly what that “Asynchronous” word means, what problems it creates, and how they can be effectively managed, next the YUI Browser History object will be examined, finally handing control of Ajax applications back to the user via their familiar back button.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Plus

5 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. How do I subscribe to the PHP podcast feed?

  2. Lorna Mitchell said

    Pick up all the various sorts of feeds and find out more about the DPCRadio series here: http://techportal.ibuildings.com/dpc-radio/

Continuing the Discussion

  1. State & Ajax – How to Maintain Browser and Application State in an Asynchronous World linked to this post on May 11, 2010

    [...] the original here: Click Here…Read Other Interesting Posts in FacebookAre You Harming Your Local Country SEO Performance?Local [...]

  2. Ibuildings techPortal: State & Ajax - How to Maintain Browser and Application State in an Asynchrono | Development Blog With Code Updates : Developercast.com linked to this post on May 12, 2010

    [...] podcast recording from the 2009 Dutch PHP Conference sessions, Paul Reinheimer’s look at maintaining state with Ajax (”in an Asynchronous World”). This talk will examine the two greatest problems in [...]

  3. Webs Developer » Ibuildings techPortal: State & Ajax – How to Maintain Browser and Application State in an Asynchrono linked to this post on May 12, 2010

    [...] podcast recording from the 2009 Dutch PHP Conference sessions, Paul Reinheimer’s look at maintaining state with Ajax (“in an Asynchronous World”). This talk will examine the two greatest problems in [...]

Some HTML is OK

(required)

(required, but never shared)

or, reply to this post via trackback.