Do you have a .NET Passport identity? You may not realize it, but chances are
reasonably high that you do. If you have a HotMail or MSN account, Microsoft
assigned a Passport identity to you automatically. Microsoft claims to have
more than 160 million users registered in the Passport identity service.
Pretty soon you'll need a Passport ID to have any interaction with Microsoft.
In December 2001, quite a few gamesters were surprised to discover that their
old accounts at the Microsoft Zone gaming site wouldn't work without a
Passport ID. Microsoft also requires a Passport ID to join MSDN, to register
for a Microsoft seminar, or to access Microsoft's node in the UDDI public
registry. The new Windows XP Product Activation (WPA) system uses Passport by
default. You can also use your Passport ID to log in to your XP system.
So just what does a Passport identity do for you... (more)
How do you define a Web service? If you ask five people to give you a
definition, you'll probably get at least six answers. Is a Web service any
application that can be accessed over the Web, or is it limited to
applications that expose a programmatic interface? Is it the code that
implements the service or the interface to the code? Do you have to use SOAP?
What about XML-RPC? Or RosettaNet? Or FIXML? Or some other XML protocol? And
do you have to use XML? Does SWIFT qualify as a Web service?
I know that many people will disagree with me, but my basic definition is as
follows: ... (more)
When discussing Web services, most people tend to focus on the core Web
services framework (the standards and protocols) and the applications that
you can build with the framework. Although I have no trouble waxing profusely
on these topics, I get even more jazzed when I start to think about
infrastructure-level Web services. (I know. I need to get a life.)
Infrastructure-level Web services are Web services that implement part of the
distributed computing infrastructure. They help other Web services
communicate. In particular, these services make the Web services framework
more ... (more)
There is an old saying among standards wonks: "The most wonderful thing about
standards is that there are so many of them." And this truism is more
applicable today than ever before. There are so many WS-* specifications,
I've started referring to them as WS-Vertigo.
But there is a reason that there are so many of them. The Web Services
Framework (WSF) relies on a composable architecture. One of the primary
tenets of the WSF is to keep things as simple as possible. Therefore, if an
application doesn't require security, reliability, or transactions, you
shouldn't clutter up the i... (more)
UDDI (Universal Description, Discovery and Integration) is a registry for Web
services. It provides a mechanism to advertise and discover Web services.
Although you don't need to use UDDI to implement a Web services solution,
you'll find that a UDDI registry greatly simplifies the management and
administration of your services, particularly once they have reached a
certain critical mass.
Once you've developed more than a few services, and once you start giving
access to those services to more than a few controlled individuals,
management starts to get more challenging. Potential... (more)