Ajax buzz continues to be high. And Thom continues to write about implementation experience, in this case looking at how one might work with standard protocol exchanges with SRU.

The initial impetus for changing to AJAX for Web applications is to improve the user experience by avoiding screen refreshes and increasing the speed of interaction. Another benefit, however, is that others can take the services your application is built on and build new ones. I reported earlier on an experiment by Mike Teets with Google maps. His first prototype broke after two days because Google changed something in their implementation. This is the sort of thing that an implementation based on standard protocols would help avoid.

[Outgoing: AJAX and standards]

More from
The technology career ladder

The technology career ladder

Library leaders should be drawn from across the organization. Any idea that technology leaders are overly specialised or too distant from general library work is outmoded and counter-productive.
Lorcan 7 min read

Lorcan Dempsey dot Net

The social, cultural and technological contexts of libraries, services and networks

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.