|
|
|
Origin: CRMDaily (www.crmdaily.com) Martin Butler, president of analyst Butler Group, warned companies not to invest in Web services too quickly, unless they have important reasons to adopt. Even then, taking a measured approach is critical, he added. "Caution is the keynote," he told delegates attending the analyst group's Web services symposium in London. "Web services is a long haul -- the dream of being able to connect systems in a real-time manner will not materialise for many years." Butler said a number of areas surrounding the core Web services standards of extensible markup language (XML), universal description, discovery and integration (UDDI) and simple object access protocol (SOAP) still need to be expanded and developed if the technology is to succeed. "Web services needs surrounding infrastructure, such as charging models and the development of grid computing. Strong parallel technologies are still developing," said Butler. Mark Quirk, head of engineering for .NET at Microsoft, agreed that current Web services have a number of shortcomings. "Our number one priority is improving security," he said, adding that reliable messaging and transaction support are also areas in need of improvement. Quirk also admitted that applications for Microsoft .NET have been slower to evolve than originally expected. "Over the last two years, we've seen the reality that everyone will take time to get used to Web services. In particular, consumer use is further out than we expected," he said. At present, Butler said, Wweb services are finding their greatest use within companies as a means of improving integration, through small experimental projects. David Keene, Oracle product manager, said he had seen significant use of XML, SOAP and Web services description language (WSDL), but fewer implementations of UDDI, required for discovering Web services across organisations. Oracle has developed a Web services implementation for Infomedics, a Dutch healthcare firm. Adrien Rietberg, chief operations officer for Infomedics, said one problem for Web services is inconsistent support for standards across applications. "As this is so new, we found that not all products support features such as SOAP messaging. We have used J2EE as a consistent and mature base to support future developments," he said. |
| |
Copyright 2002© EHTO All rights reserved EHTO is not responsible for the contents of external websites it links to. Mail suggestions to: webmaster@ehto.org |