February 2004 - Posts
Indigo is subject of the latest MSDN TV Episode. Check it out.
John Shewchuk has been one of the major players in the design and creation of Indigo, and so I invited him to come on the show and share with us some of his background and insights regarding how applications might be able to build upon a common communication framework. And to show us how Indigo fits into the programming model, I invited Steve Swartz to walk us through some code which illustrates how easy it can be to work these features into your applications.
In the past, building this level of inter-application communication has almost been rocket science. It was difficult, complex, and time consuming to assemble all of the necessary components, and often very design intensive to get it properly worked into your overall application design. Hopefully this episode will show you how we've been able to streamline this process.
Fresh from the news at the RSA conference:
Web Services Interoperability Organization (WS-I) announced the availability of the first Security Scenarios Working Group Draft for public review. Developed by the WS-I Basic Security Profile Working Group, the Security Scenarios document identifies security challenges and threats in building interoperable Web services and countermeasures for these risks.
Download the Basic Security Profile Security Scenarios from the WS-I site.
Let's see what Richard Turner comes up with in the next few weeks. At least it looks promising from what he writes in his first post:
So what are you going to find here? Well, to give you some idea, I am a program manager at Microsoft working on “Indigo” and have interests in:
- Software and Systems' Architecture - OOD, Service Orientation & Service Oriented Architecture
- Code migration from existing technologies to “Indigo“
- Performance - making services fly!
Sounds like a good mixture to me.
Frankly, I was a bit astonished that there wasn't more feedback on my soliloquy the other day ... are people already happy with what is present in the Web services stack? Especially the interesting corner of metadata. How do you see the whole game?
Anyway, this time I have a new finding. You all know WS-Policy & friends. I also talked about its features and capabilities in the other post. And, obviously, you all know WSDL - I mean WSDL 1.1. So, ever heard about WSDL 2.0? Go and read a bit through the spec (read it thoroughly if you are a plumber ;-)).
Browse for the WSDL Feature Component feature, ah. No, it is not a replacement for policies, don't worry ...
Jason Clark has a new article on MSDN from an upcoming book on Indigo: Inside "Indigo," Chapter 2: The Journey of a Message:
Now it's time to take a closer look at the message itself. In a messaging application, the message is the fundamental unit of communication between two nodes on a network. The message can relay information, suggest or demand a course of action, or request data. In this chapter, you'll find out what constitutes a message in SOAP version 1.2 and how messages are structured, including what kind of content they can contain. You'll then follow the path of a message as it makes its way from a sender to a receiver in an "Indigo" messaging application.
Very good read - love is the message and the message is love ...
A more or less philosophical discussion about Web services with business relevant implications. Interesting read.
Related to this - as mentioned in the artcile - you owe yourself a look at this - at least the concepts make a story to base on, IMHO.
ZapThink has a nice article on when you are not supposed to use SOA.
Für alle interessierten Entwickler, die sich mit Web services auseinander setzen wollen oder müssen präsentiert MSDN Online Deutschland einen mit Microsoft LiveMeeting-Technologie durchgeführten Web Cast zum Thema Web Services Enhancements 2.0.
Webcast zum Thema Web Services Enhancements 2.0
Termin: 26. Februar 2004, 16:00 – 17:00 Uhr
Thema: Webservices Enhancements 2.0
Referenten: Dariusz Parys und Christian Weyer
Hier die Beschreibung des Web Casts:
Web Services-Enhancements 2.0 - Next Generation Web services heute
Viele sprechen von der nächsten Generation von XML-basierten Web services. Mit den Web Services Enhancements für Microsoft .NET (WSE) kann man diese Vision schon heute Realität werden lassen.
Mit der neuen Version 2.0 halten neue Features in den Bereichen Sicherheit, Policies und SOAP Messaging Einzug in die Web Services-Landschaft. Gepaart mit einem mächtigen und dennoch einfach zu verwendenden Programmiermodell können die WSE auch für Ihre Projekte ein Erfolgsfaktor sein.
Im Rahmen des von Dariusz Parys moderierten Webcasts hält Christian Weyer einen Vortrag zu diesem Thema.
Termin: Donnerstag, 26. Februar 2004, 16.00 bis 17.00 Uhr
Microsoft and friends (but without IBM) released the WS-Discovery specification as part of the metadata pillar of the Web services Architecture.
WS-Discovery enables advertisement and dynamic discovery of services on both ad-hoc and managed networks. Services may be organized in a hierarchical scope, and clients can query for services by type as well as scope without heavy administrative costs. This specification enables numerous design patterns for enterprise services; provides a discovery architecture for peer-to-peer services like buddy lists, websites, and file shares; and forms the basis for discovering network-attached devices such as printers, cameras, and PDAs.
Web Services Dynamic Discovery (WS-Discovery) specification was designed to:
-Allow discovery of services in ad hoc networks with a minimum of networking services -- e.g., no DNS or directory services
-Leverage network services to reduce network traffic in managed networks where such services exist
-Enable smooth transitions between ad hoc and managed networks
-Enable discovery of resource-limited service implementations
-Support bootstrapping to other Web service protocols as well as other transports
-Enable discovery of services by type and within scope
-Leverage other Web service specifications for secure, reliable, transacted message delivery
-Provide extensibility for more sophisticated and/or currently unanticipated scenarios
-Support both SOAP 1.1 and SOAP 1.2 Envelopes
Hm, smells a bit like DISCO, WS-Inspection, paired with Jini - and mixed with the current hype and movement of mobile devices. Added a little piece from the basic ideas of UPnP and Rendevouz.
And all in a sudden WS-Inspection is gone from the specification index page ... (which makes sense in that case).
OK, now we can discover any services on any devices (WS-Discovery), can discover services categorized by certain common and custom schemes and classifications (UDDI) - now we still need to be able to discover the runtime capabilities and requirements of services described through policies. Still desperately seeking WS-MetadataExchange ...
If you want to consume an Indigo Web service from the 'Add Web Reference ..' dialog within Visual Studio .NET or with the command line tool wsdl.exe, or with WsContractFirst, the Indigo service must be using Datagrams over HTTP.
Dialogs and/or TCP are not supported by the .NET Framework 1.x (which is the common base for all three tools).
More Posts Next page »