In part one, Hackman talked about Tibco's vision of SOA business applications and its Ajax Message Service (AMS), which is designed to provide event-driven SOA by pushing live data and events from servers to Web pages, Ajax applications and other software.How easy has it been to tie what you've done in General Interface into the larger SOA message that Tibco has?
People are thinking at a variety of levels. We have customers who use SOAP in 50 percent of their efforts. Some people automatically associate Web services with SOAP, but they do that when there's anticipated a high degree of reuse for that effort. They get the return on that effort from taking the extra time to create that, but some organizations are deploying Plain Old XML for something tactical or solutions where they know the services and solutions aren't going to have a high degree of reuse, therefore they don't invest in that overhead. Both are example of service orientation, decoupling the client, no longer tightly coupling the HTML page to the application information. But whether they go that extra level to embrace the full WS-* standards or UDDI is based on the application and the intent of the application. So we see both. Large caps SOA and lower case soa implemented in organizations. Are you running into REST these days?
That's the question. Obviously, time will tell. The types of problems that seeks to solve tend to be more this whole sort of cinematic user experience that's out there that Flash has addressed in the past or what (Microsoft) SilverLight is trying for. It's pretty transparent that they are trying to displace Flash. There's a little new plug-in war, if you will, that's going on in those areas.
The core thing about Ajax is it works with the technology you already have. The adoption rate for Windows XP was eight years to get above 60 percent. The nice thing about Ajax is it works on Windows 2000 workstation server. So there's a real value to working with old tech. What's cool about Ajax is it's all these brand new capabilities using these old technologies. In fact, that's exactly how the Wall Street Journal when they covered Ajax for the first time in mid-March of 2005 described the Ajax phenomenon. Ajax has a potential very long life because you can use it today rather than have to wait for tomorrow's adoption.