This post originated from an RSS feed registered with .NET Buzz
by Scott Hanselman.
Original Post: Wizzy wizzy wizzy
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
Great time tonight at the Cleveland .NET Special Interest Group. We started
at 6pm and were still going towards 9pm. Not bad for a talk that was supposed
to be ~ an hour. Great crowd, standing room only and GREAT questions.
Covered the history of everything from The Big Bang, DNA, up till that evening.
One of the big topics o' interest was WSE 2.0, and Web Services Security. We
spent a lot of time (over 60 minutes) just talking about separating Domain Object
implementation from Messages from Transport Protocol. I showed my boss Chris
Brook's great single implementation/multiple transport of a Web Service
using WSE 2.0. With a single chunk of imp code (via his "imp factory") we support
multiple flavors of Web Services using ASMX, WSE 2.0 SOAP and more importantly WSE
2.0 SOAP over TCP Sockets! Very cool.
We talked about the clear possibility that we could support SOAP over other transports,
and Queuing came up often. So, I retire to the hotel and what do I see?
$d(Synchronicity). My friend Christian
Weyer pointing us to an upcoming(?) MSMQ
Transport for WSE and an existing(!) MQ
Transport for WSE. Great stuff from Kevin
Hammond who today has MQSeries and who is refactoring MSMQSoapProvider for
async support. Where/When are we getting these bits?