Wednesday, September 21, 2005

Talking about Today's Web Service Stack: ASMX 2.0 + WSE 3.0

It goes without saying that most will start using the Indigo as the delivery platform once released due to its intensive focus on SOA, the question remains whether one should focus on Indigo or the ASMX/WSE3.0 at this point? (both are in beta releases). Aaron's blog item, Today's Web Service Stack: ASMX 2.0 + WSE 3.0 compares by listing out the comprehensive feature set supported by Indigo and ASMX/WSE3.0. My gut feeling is to shakeup a little and start concentrating on Indigo keeping in view the advantages Indigo brings in. Indigo offers most choices for the enterprise. But its a consolation for the others who decided to stick in at this point with WSE that they can flex whenever they decide to move to Indigo with ease, since the feature set more or less complements rather than competing.
Aaron Skonnard
Today's Web Service Stack: ASMX 2.0 + WSE 3.0

Tuesday, September 20, 2005

.NET and J2EE Interop resources by Ryan

.NET and J2EE Interop Resources list by Ryan Storgaard
Ryan Storgaard's Blog - Microsoft ISV Developer and Platform Evangelist : .NET and J2EE Interop reso

Gartner:Web Services Vendors: Who's Leading and Who's Innovating?

Discussion on Web Services vendors and their competitive strengths at Gartner website. A presentation and the audio recording of the teleconference are available for download from the website.

Web Services Vendors: Who's Leading and Who's Innovating?25-May-2005

Friday, September 16, 2005

MSDN Webcasts on Web Services

Here is a list of Webcasts available at MSDN. Most of the webcasts can be downloaded for off-line viewing.

Web Services (Level 300)
Web Services and Services Oriented Architecture (Level 200)
Web Services Update (Level 200)
Building and Consuming Web Services (Level 200)
Developing in the Web Service Playground (Level 300)
Using Asynchronous Patterns with Web Services (Level 300)
Application Decomposition for SOA Based Systems – Level 300
Service Patterns
Web Services Security Patterns (Level 300)
Web Service Standards Past, Present, and Future – Level 200
Defending Your Web Services—Level 200
Designing Services for the Long Term in Service-Oriented Systems (Level 300)
Patterns for Service Oriented Architecture—Level 200
Let's Learn About the WS Standards: Standards that Promote Interoperability between Web Service Implementations (Level 200)
WS-I Basic Profile
WS-I Base Profile (Level 200)
Web Services Interoperability Profile 1.0
WS-I Basic Profile Security Sample Application (Level 200)
WSE 2.0
Geek Speak: WSE 2.0 Introduction—Level 200
Implementing Routing and Attachments using WSE 2.0 (Level 400)
Securing Web Service Communications with WSE 2.0 (Level 400)
Web Service Message Transmission using WSE 2.0 (Level 400)
Managing Web Services Using WS-Policy in WSE 2.0 (Level 400)
Using Web Service Enhancements 2.0 for Messaging – Level 300
Integration & Interoperability
How to Design Your Web Services For Successful Interoperability (Level 200)
Interoperability and Integration Using Web Services– Level 300
Integration Patterns – Level 200
Microsoft .NET - J2EE Application Interoperability – Level 200
Microsoft Integration Technologies: When to Use What (Level 200)
Interoperability and Integration using Web Services - An Industry Perspective – Level 200
Governance and Compliance in Service-Oriented Solutions—Level 200
Security and Interoperability with WSE 2.0, WebLogic and Axis (Level 300)
BizTalk Web Services and WSE (Level 200)
Programming with the MapPoint Web Service (Level 200)
Design and Architecture for .NET Applications - Level 300
Using Web Services To Connect to SQL Server 2005 from Your Smart Client Applications (Level 200)
Using Web Services with BizTalk Server 2004
Best Practices for Implementing Effective Service-Oriented Architecture (SOA) Governance - Level 200
Web Services Orchestration, Management, and Security - Can They Play Together?
Increased Agility with Web Services
WSI Migration to WSE 3.0 and .NET 2.0 (Level 300)

Wednesday, September 7, 2005

Talking about Microsoft's Ballmer Threatened To 'Kill' Google? -

All the News Media houses started creating a BIG issue around the testimony by a former Microsoft employee who is currently working at Google. One of the issues is about Ballmer, who supposedly told that he would kill Google. I wonder why was it such a big surprise? Go to any Board Meetings or Open house meetings of any corporate, every body in the meeting say they would like(die) to see the end ofl their rivals. Why is it a surprise. They are rivals. And every corporate in America is trying to kill its rivals. And the entire Corporate America is trying to kill the Corporates across the world. That is what they call the Competition. I don't see any thing unusual in this. Google is trying to kill all other search engine companies. Skype is killing most of the telecom big heads. Bloggers are killing the hypocritic traditional media houses. So what? Anything unusual? Everybody is trying to kill somebody else, for that matter. Not all businesses complement each other. They compete with each other, and whether they say it or not they are trying to kill the other. They must have said it. They must have said it millions of times.
Microsoft's Ballmer Threatened To 'Kill' Google? -

Quality of American Cars - Inherently inferior?

By looking at the largest Auto recalls in America's history, I am wondering whether American made cars inherently of inferior quality? All top 5 Largest Auto Recalls are from either Ford or GM. The number of vehicles recalled is huge (around 28 million vehicles), indicating that the problems are found long after the the release or the companies ignored the results obtained during their internal tests assuming that the problems would not surface. Or the companies acknowledged the existence of a problem in thier vehicles after a long time the first incident is reported. Eitherway, recall of such a huge number of vehicles would cost them very dear. Would it have been prevented if they had spent some more money on the testing?
Quality is costly. But lacking it, always costs a lot more. - Ford recalling 3.8 million vehicles - Sep 7, 2005
"-- In 1996, Ford recalled 7.9 million vehicles for faulty ignitions
-- In 1971, GM recalled 6.7 million vehicles for engine failure
-- In 1981, GM recalled 5.8 million vehicles for a rear axle problem
-- In 1972, Ford recalled 4.1 million vehicles for a shoulder-belt problem" : Fact or Allegation ? Just another twisted title for sensationalism

This is yet another example of’s sensationalism twisted titles. The title says, as if this was a fact, woman made to urinate in pub...