moderately inappropriate

WSE2 is neat sometimes

So, as some of you know, I have been working on implementing parts of WSE2 on mono. There are plenty of potential issues with this, as it isn't yet a fully finished spec, so there are most likely going to be some changes. My fingers are crossed that the changes to the API are minimal at best.

However, one potential change I would like to see is this:

Running the following code results in this exception:

"Unhandled Exception: System.ArgumentException: Host name 127.0.0.1 does not represent the local machine (__LOCALHOST__)" with __LOCALHOST__ signifying the hostname of your wonderful windows computer.

SoapReceivers.Add(new Uri("soap.tcp://127.0.0.1/WSE2_Madness"), new MySoapReciever());

Now, it seems to me that this should work fine, one of the things I liked best about soap is that it shouldnt care where this message is sent to, just that it received it. The other great thing about WSE2 for me was the ability to send soap messages over tcp with ease, http's overhead is just something that isn't always needed and it was wonderful to see MS recognize this.

However, by forcing addressing based on windows host names, this seems like one of the potentially greatest features of WSE2 is going to be by and large relatively useless for the general public.

I could be misunderstanding the spec, or missing an important piece, and if so, I hope I figure out what it is, and grok it ASAP, because this is a potentially wonderful API that I hope gets major use.

Hopefully soon I will have some good news about the Microsoft.Web.Services.Addressing namespace working :)

Posted by tberman at October 7, 2003 03:02 PM