After a few days off working on a top secret project, I am back to post another weblog. Okay, so the project is not top secret, and I didn’t really have a few days off. I was working for my employer Avanade. I’m really just looking for another excuse to test blogger new e-mail feature.
It is always nice to test betaware. I submitted the posting below on April 20. Talk about net lag in e-mail.
System.Xml.Serialization namespace in .NET totally kicks ass. It makes consuming and producing XML almost as easy as writing a class definition. Let me explain.
Nice and quiet in New York City today. Rain and cooler temps…yey! I’m happy. The rain earlier canceled my roller blading plans but chillin’ in the apartment turned out to be a good thing.
Bahahahaha…being new to CVS, I really enjoyed this quote, “TortoiseCVS was orginally based on the source code for WinCVS, a more comprehensive but complex to use client. Many thanks to them!”
Over the years, I have read a lot about the Open Source “movement” and I have been a fan even though I never really participated in an open source effort. I have written a number of freeware applications in my time and now I wish those efforts had been open source.
A lot of cool things have come out of the Open Source community. The one area that has me totally jazzed is the development tools such as CVS, TortoiseCVS, and SourceForge.net. These products are amazing and have me wondering why these great development aids are not used in larger corporations.
I understand not relying on open source for mission critical applications that businesses depend on to survive and gain their competitive advantage. And for years I have worked with companies where the IT staff consistently complain about working with inefficient development tools such as Visual SourceSafe. But tools like these do make sense in the corporate environment. Speaking for one developer, myself, I would be happy if these tools were part of my daily development environment.
Just when you thought swing technology could not be any better, some guy is issued a patent on side to side swinging. Yes, swinging! The activity most of us enjoyed as a kid. Hopefully the guy will not expect retroactive royalty payments.
Speaking of patents, I have invented a new way to scratch an itch. When I haven’t shaved in a day or so, I will scratch my arm with my chin. I hope to have the patent papers submitted later today.
ZDNet: Tech Update: Enterprise Applications / IBM drops Internet patent bombshell: A recent IBM patent claim could threaten royalty-free access to a key Internet standard protocol backed by the United Nations. The standard–called ebXML–is an XML-based set of definitions for electronic transactions and business collaboration.
What UDDI is not? It is not an execution environment for web services.
Recently I have had a number of conversations regarding UDDI and the implementation of private UDDI nodes within the enterprise. During these talks, I’ve noticed a common misunderstanding with regard to UDDI at runtime. It seems that many think of UDDI at runtime as a means to execute a web service. However, UDDI is not an execution environment but one of a number of ways to discovery services.
There are some interesting uses of UDDI at runtime though. One use is to determine the end point to a web service at runtime. This eliminates the need to hard code the end point address in the application. This type of abstraction layer could be used to provide greater reliability within the application in much the same way DNS provides greater reliability verses direct use of an IP address.