So now we know at least part of the client side development that the Kirland Google team has been working on-- see David Bau's post on Google Talk on the Google blog.
If you connect the dots, you can infer much of the rest of what they must be working on. Back in June, Adam Bosworth was writing in Ajax Reconsidered about how the browser isnt good at listening to external events, such as 'an XMPP message or a VOIP request or a data-changed post for an ATOM feed.'
The XMPP comment was a clear leading indicator of Google Talk. Anyone reading carefully between the lines might have broken the story months early. Let's suppose that the rest of the message is also a leading indicator of what Google would like to do with the browser
Sunday, August 28, 2005
Subscribe to:
Post Comments (Atom)
Popular Posts
- AS400 Job Scheduler
- Configuring Tomcat5 and Apache2 with Virtual Hosts using mod_jk
- What is RPGsp (RPG Smart Pages)
- What is LANSA
- EclipseZone - Clean Up Warnings with the 'restriction' Suppression Flag
- Using as400 QRCVDTAQ api to retrieve a message / entry from a dataqueue
- Common Gateway Interface (CGI) on the as400 / iSeries
- Formatting and sorting dates in Displaytag
- AS400 APIs
- Adobe Flex 2.0 Beta
No comments:
Post a Comment