XML Web Services: Means to an End
An anonymous reader writes "For the second day in a row at the XML Web Services One conference here, a keynote speaker got up and signaled the impending end to the Web services era, at least on a standards level. Don Box, an architect in Microsoft Corp.'s developer division told an audience of Web services conference attendees Wednesday: 'The end of the XML Web services era is near. I predict two years from now we won't have this conference.'"
"protocol work is starting to wind down, the infrastructure is catching up with protocols and it's time to start thinking about applications."
... but suitable applications aren't that obvious ... or maybe I've missed the point.
;). Why change what already works?
This quote sums up Web Services for me. The infrastructure/concept is okay
A relative works for MS (partly promoting Web Services) and keeps telling me that we should consider creating Web Service applications and/or converting existing applications to Web Services. My standard answer is that we can't afford to run Microsoft products on remote servers, both practically and financially. But of course the real reason is that I don't want to