Writing specs just for the spec of it?
From InfoWorld: SOAP Author says enough specs already, and I agree. I wonder how many eager engineers have sat down to architect their first WS-based application after learning all there is to know about SOAP, WSDL, and UDDI, but run screaming when they see the neverending stack of additional WS specs? For internal apps there's less concern for issues like routing and referral, but I have to really feel for the B2B folks out there.
On the one hand, you want to take full advantage of all the great things about WS NOW - on the other hand, you don't want to deploy an application that isn't going to meet some handshaking criteria a few months down the road.
10:40:51 PM 
|
|
