I've been posting some comments about Indigo on my other blog - feel free to subscribe if you're interested in Indigo. Here are some of the Indigo entries I've written: http://galactic-patrol.blogspot.com/2005/02/indigo-is-re-released-into-wild.html http://galactic-patrol.blogspot.com/2005/02/to-indigo...

Hank Wallace posted a question recently about the <NotifyTo> element in a WS-Eventing subscription request, and whether it really needed to contain an <Address> element or not. You can read my response in the comments, but while I was looking over the specs I realized that the presentation...

A bit of terminology discussion here… In a recent article , Yasser introduced this following use of the word ‘anonymous’: “ An application comes to life on the network by using an Indigo port, which acts as the gateway between the application and the network. Each port is identified...

I’ve noticed that Rich Turner has been posting some excellent Indigo posts recently on his blog – go check it out!

A co-worker of mine kindly pointed out an error in my WS-Eventing messages; the <NotifyTo> element contains an <Address> element, not a text string. I’ve corrected the previous posts. My apologies for any confusion.

Ok, now pay close attention; this part gets real complicated. The required elements of a notification message (that is, the shark-attack message sent to the subscriber) are as follows: … That’s right, there are no required elements. Any SOAP message can be a valid notification. The...

Before I talk about the optional elements on a WS-Eventing subscription, I’d like to quickly cover the response message you get back when your subscription request is accepted. Taking a Header Most of the stuff in the response message header is just bits of information from your request header...

In part I of my discussion of WS- Eventing , I deliberately left the namespaces off the elements of the SOAP message. I did this for clarity, but I feel a little bad about where I say “This is finally valid WS- Eventing ” – because its really not completely valid without the namespaces...

WS-Eventing is a standard that enables interoperable publish/subscribe systems. The spec itself is quite short and sweet – I recommend taking a look at it. As a tester, I’m quite pleased by the simplicity because it makes implementations easier to test (and hopefully more robust). I hope...

I noticed the WS-Eventing proposed standard has been published – this is directly related to the Indigo feature area I work on.

I published this info when I started my GotDotNet blog ; with the move, now is a good time to re-present the info: Bruce Williams I am a test developer for Indigo – current and future Web Services technology at Microsoft. e-mail : bwill@microsoft.com IM: domanite@hotmail.com

Doug is asking folks if we should change how [Serializable] works under partial-trust, to be more compatible with our upcoming XML serialization efforts.  Follow this link and let him know what you think .