snellspace : a perfect world spoiled by reality


Tuesday, February 05, 2002

Simon thinks the message element should go away also.
6:10:42 PM    

IBM, Microsoft, BEA Systems to partner on Web services (InfoWorld)
6:07:41 PM    

CNN.com - Mr. Potato Head still hot at 50 - February 5, 2002 - You know, I kinda feel deprived.  I never had a Mr. Potato Head growing up.

And speaking of a bunch of Potato Heads....


6:01:24 PM    

Getting on a plane Sunday to fly back east for a week.  First trip since getting stuck back in Raleigh last September.  If, on the off chance, there happens to be any terrorists reading this, next week is NOT a good week to plan anything.
5:56:26 PM    

Keith says: "Transport agnostic roll-over seems like a huge win, IMO"  Sure, if it wasn't for the total lack of reliability, security, and less than stellar performance.  IMHO, UDDI is too fat for serious runtime fail over.  I mean think about it, if you're a manufacturer and you need to order some parts for immediate shipment, but you can't get a hold of your favorite supplier, are you going to go trudging around through the yellow pages looking for a replacement or are you going to already have a replacement lined up and programmed into the speed dialer on your phone?  It just doesn't make sense to wait until something fails to go out discover a replacement service.  The disadvantages, in this case, far outweigh the advantages.
5:49:51 PM    

Giants forging Web services consortium. Microsoft, IBM, Intel and BEA Systems plan to educate businesses on how to build Web services and how to ensure they do it in a compatible way, according to sources. [CNET News.com]
5:35:37 PM    

Ok, so I have a question.  Is the WSDL message element really necessary?  Personally, I say no, it's not.  We could get by very well without it by using XML Schema complex types.  Given a choice, I'd vote this as the first thing to go in the W3C standard.  Whatcha think?


9:44:57 AM    



Copyright © 2002 James Snell.
Last update: 6/25/2002; 9:48:34 PM.
The views and opinions expressed on this site are solely those of the author, James Snell, and not necessarily of James' employer.