Interested in Indigo?

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-clr-contract-is-not.html http://galactic-patrol.blogspot.com/2005/02/serviceoperation-wheres-message.html http://galactic-patrol.blogspot.com/2005/03/indigo-testing-take-pretty-things-and.html http://galactic-patrol.blogspot.com/2005/03/got-indigo-questions.html http://galactic-patrol.blogspot.com/2005/03/whats-right-way-to-dispose-channel.html Fair warning, I do occasionally blog about non-technical topics.

1

WS-Eventing and WS-Addressing

 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 of this containment is a bit confusing….

0

What is an ‘anonymous’ sender?

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 by a unique URI known as the port’s…

4

Rich Turner’s Indigo Blog

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

0

Errata for WS-Eventing posts

 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.

0

WS-Eventing Part III: The Notification Message

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 event source and the event sink (aka the subscriber)…

10

WS-Eventing Part II: The Subscription Response

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, regurgitated back to you; your <ReplyTo>…

11

WS-Eventing: A Note on Namespaces

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.  So to salve my conscience,…

2

WS-Eventing for Dummies

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 that you, as developers writing to the spec,…

29

WS-Eventing published

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

0