Series: Web 2.0 for Lotus, WebSphere Portal and You Listen to Pete Janzen from IBM Lotus interview various experts from the Lotus and WebSphere Portal development teams on Web 2.0 technologies. Hear how IBM has utilized these technologies in the various products and how you, the developer, can leverage them in your custom applications.
Abstract for Using Web 2.0 inDomino: Vinod Seraphin looks at how the Lotus Domino platform supports various Web 2.0 technologies. Hear how developers were using Ajax in Domino applications before the term Ajax was coined and how Domino's support for Ajax has evolved. You'll also hear how Domino Web Access can be viewed as one of the earliest rich internet applications and how developers can use similar techniques in their customapplications. Vinod Seraphin is the lead architect for Domino Web Access.
Discussion: JANSEN: Welcome to our developerWorks podcast series on Web 2.0 as it
applies to various Lotus and WebSphere Portal offerings. My name is Pete Jansen, and I'm the product manager for Lotus Component Designer and Enterprise Integration for the Notes and Domino platform.
I am your host for this podcastseries where I will interview a number of our technical thought leaders on topics related to Web 2.0. Our objective is to enlighten you on the various concepts and technologies that comprise Web 2.0, and how they apply to the products we develop.
In this podcast we will explore the topic of Web 2.0 for Domino. I am very pleased to welcome Vinod Seraphin who is a senior technical staffmember at IBM and the chief architect for Domino Web access.
Vinod has been instrumental in leading the adoption of Web 2.0 technologies like Ajax and Domino even before the term Ajax was coined. Welcome to our podcast series, Vinod.
Hi Pete, thank you.
You've been involved with Domino for a long time, and I think that you
can really share a lot of good insight onhow we go ahead and have leveraged Web 2.0 in the past and, you know, how we're doing it now. And then maybe some thoughts on the future.
But what I'd like to start off with is, you know, looking back a little bit, since Domino has a long history of the Web application platform, could you please outline how Domino has evolved its support for building Web 2.0 style applications?
SERAPHIN:Yes, so I think Domino goes way back and it sort of evolved along
with the Web. So if you look at the early releases of various standard templates we ship with Domino, they have a very Web 1.0-ish, meaning that you would make a URL, it would come back with a static page.
There wouldn't be that much interactivity with the page without reloading another page. And over time, that's, you know,Domino has evolved to provide more of those dynamic capabilities.
And I think those dynamic, you know, better, richer experiences for a user using a browser is part of this Web 2.0, is one of the core things that's part of the Web 2.0 umbrella.
And so if you wanted to outline how we evolved, how Domino evolved to allow more interactive applications, you know one of the first thingswas probably around the Domino 5 timeframe where Domino introduced a view applet. And the view applet was used so that when you're in a view it wouldn't reload that page for the view but rather would go get newer data segments based on how the user was interacting with the applet. So as they scrolled in the view, the applet would go out and retrieve that chunk of data.
And so I think that wasreally the original background for how the read view entries URL command first developed and along with that applet was also using read design and something else called read entries. And so those were some of the early sort of like Rest APIs that were supported by Domino 2 to do that.
In addition, Domino has always had a very rich set of design elements that could be used in lots of different...