Browse by Tags
Last year I described the general structure of WSDAPI's WSDXML sections and provided some hints for creating and consuming these structures. I've received a few requests since then to provide more concrete examples of how to build these structures in
Read More...
OASIS has just announced that version 1.1 of DPWS , WS-Discovery , and SOAP-over-UDP are now officially standards! The links to the RDDL and spec pages currently point to the Committee Specification 1 (CS1) revisions of the specs, but OASIS will update
Read More...
The SOAP Message Transmission Optimization Mechanism is a building-block spec that DPWS profiles so that specifications built on top can use it in a consistent and device-friendly way. MTOM isn't used in any of DPWS's messages, but it is available to
Read More...
It's been a while since I last provided an update on the standardization of DPWS, WS-Discovery, and SOAP-over-UDP. I'm pleased to say that the standardization committee has produced Committee Specification versions of these three specs--that doesn't mean
Read More...
Traditional big web services, like a billing system or a service running in the cloud, nearly always have fixed addresses--often HTTP URLs. Smaller web services, such as those on a PC or a device, often have logical identifiers ("urn:uuid:c3de740f-9227-4706-b3ee-9494243c040d")
Read More...
DPWS defines two different levels of metadata: the Device delivers metadata about the entire device, and about the relationship between the Device and its Hosted Services; and each Hosted Service delivers metadata about itself (and optionally about its
Read More...
The roles of Types in WS-Discovery messages is really clear for generic, non-DPWS services. Types are qualified names expressed in the <d:Types> element of WS-Discovery messages, and these names identify a set of operations; the service advertised
Read More...
Just under six months ago, DPWS, WS-Discovery and SOAP-over-UDP entered standardization in the OASIS WS-DD technical committee . An incredible amount of work and progress has been made during that time, and the committee has just published the second
Read More...
A lot of WSDAPI objects implement IUnknown , so the expose the Release() method. A few more also support Terminate() . What's the difference, and which should you call? Ultimately, you should always refer to the documentation , as rules for specific objects
Read More...
It has never been particularly easy to choose a Web Services stack on which to build your application. Microsoft has produced many over the years (for example, WCF and WSDAPI) and other software vendors produce even more. The feature sets of these stacks
Read More...
WS-Eventing is one of the building-block specifications that DPWS profiles and makes available for solution authors. Some applications require the device to send notification messages back to the client; e.g., a printer sends a message to the PC when
Read More...
The Devices Profile for Web Services isn’t exactly a Profile in all senses of the word. Yes, it does select and constrain underlying specifications like SOAP and WS-Discovery, but it also does very un-profile things like define schema. One of the things
Read More...
We've just published a whitepaper on DPWS, WS-Discovery, and SOAP-over-UDP over at MSDN. This is a great guide for those of you who want a good technical introduction to how all three specifications work. Special thanks go to Ram Jeyaraman for doing all
Read More...
UUIDs (related to GUIDs ) are used frequently in computing applications. If you don't know these by name, you will probably recognize the 128-bit value in the format in which it is typically rendered: 7673868d-231e-490d-9c4f-19288e7e668d This is just
Read More...
Last week OASIS announced the formation of a technical committee to standardize DPWS, WS-Discovery, and SOAP-over-UDP. This is big news for all three specifications (and the people who implement and rely on them), as it gives us an opportunity to collaborate
Read More...
