On this page

The Indigo Programming Model
Indigo Adapter for BizTalk Server 2004
WSE: Another Compression Filters Update!
WS-Addressing makes its way to W3C
Gtk# and Glade# VS.NET 2003 SDK
WSE: Compression Filters Update
SQL Server 2005 Beta 2 at MSDN Subscriber Downloads
SQL Server 2005: CLR Hosting – Establishing Balance



The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 83
This Year: 0
This Month: 0
This Week: 0
Comments: 5

Sign In

# Friday, February 25, 2005
The Indigo Programming Model
Friday, February 25, 2005 12:33:33 PM UTC ( Indigo )

Clemens is on a roll with lots of fresh Indigo information. If you want to get a feel for the new programming model you should header over, and subscribe, to his blog.

Comments [0] | | # 
# Monday, February 21, 2005
Indigo Adapter for BizTalk Server 2004
Monday, February 21, 2005 7:29:02 PM UTC ( BizTalk Server | Indigo )

I guess the news is out!

Scott Woodgate from the Microsoft BizTalk team recently mentioned on his blog that I’ve been working on a prototype Indigo adapter for BizTalk Server 2004. And if you were one of the lucky people attending VS Live a few weeks ago you may have seen it in action on stage.

It has been great fun working with the early Indigo builds, and it is shaping up to become a truly fantastic piece of technology. There is no doubt in my mind that joining Indigo and BizTalk Server will yield a powerful combination, and I am extremely grateful to be a part of this early effort.

Now that the secret is out you should expect some more information soon.

Comments [0] | | # 
# Thursday, September 16, 2004
WSE: Another Compression Filters Update!
Thursday, September 16, 2004 7:55:39 PM UTC ( Security | Tools | WSE )

It is great to see that someone has a taken an interest in the WSE compression filters I’ve been working on. Rodolfo Finochietti has added several new features to the code base.

  • Compress attachments
  • More algorithms (Deflate, Zip)
  • Compression level (set through compression context)
  • Threshold. Compresses according to the minimum message size (body size plus all attachments size)
  • Several other improvements and code cleaning.

    This is really exciting news. Great work Rodolfo!

    You find a list of download links here, or you can download it directly from this link.

  • Comments [0] | | # 
    # Tuesday, August 10, 2004
    WS-Addressing makes its way to W3C
    Tuesday, August 10, 2004 8:23:12 PM UTC ( Architecture | Indigo | Security | WSE )

    WS-Addressing, a vital piece of XML Web Services infrastructure, has just been submitted to the W3C.

    With WS-Security being an official OASIS standard, and WS-Addressing entering the W3C standardization process, we may soon be looking at the first stable set of advanced web services infrastructure.

    These two specifications form the foundation of the Microsoft Web Services Enhancements toolkit's functionality. Perhaps we will soon say goodbye to backwards incompatibility and short support lifecycles in this particular area.

    As always, it is great fun to follow the advances.

    Comments [0] | | # 
    # Sunday, August 8, 2004
    Gtk# and Glade# VS.NET 2003 SDK
    Sunday, August 8, 2004 3:18:14 PM UTC ( General | Mono )

    Paco Martinez over at Mono has created an easy to use Gtk# and Glade# installer that not only installs all the required files, but also includes a VS.NET 2003 compliant SDK with project templates, documentation and samples.

    The ultimate goal of this installer is to provide the best development experience when creating Gtk# applications in a Windows development environment.

    So if you are looking to develop cross platform .Net Windows applications, or you simply want to give a WinForms alternative a try; head over to this blog posting for download information and additional resources.

    It’s really cool to see how the CLR platform is catching on.

    Comments [0] | | # 
    # Wednesday, July 28, 2004
    WSE: Compression Filters Update
    Wednesday, July 28, 2004 6:21:46 PM UTC ( Tools | WSE )

    I released some sample code for a WSE compression filter a few months back, and I have recently updated the code to be more in tune with the look and feel of the WSE extension model.

    Since the initial release, I have submitted the code to the Plumbwork Orange project on GotDotNet. If you are looking for the most up-to-date version then that is definitely the place you would want to look. I have also made a snapshot of just the compression code available for download here.


    This SOAP compression extension is an implementation of an idea by Martin Valland and me, and it is in no way an official specification controlled by a standards body.

    This is a prototype implementation and it comes without warranty of any kind.

    Comments [0] | | # 
    # Monday, July 26, 2004
    SQL Server 2005 Beta 2 at MSDN Subscriber Downloads
    Monday, July 26, 2004 3:48:38 PM UTC ( SQL Server 2005 )

    SQL Server 2005 Beta 2 Developer Edition is available for download at MSDN Subscriber downloads. Go fetch ;)

    Comments [0] | | # 
    # Wednesday, July 14, 2004
    SQL Server 2005: CLR Hosting – Establishing Balance
    Wednesday, July 14, 2004 2:30:06 PM UTC ( Architecture | SQL Server 2005 )

    I’ve seen a lot of posts about the CLR Hosting support in SQL Server 2005, and quite a few of them discuss the possibility of moving business code into the SQL Server engine. I think it is time to establish some balance here, and I’m going to throw in my 2 cents.

    CLR Hosting has a few obvious use cases, but it is in no way a replacement for T-SQL. If you are writing extended stored procedures then this is definitely the only logical way to go. It has a much better and safer programming model than the native one. If you are writing complex algorithms that can severely limit your result set then it is probably a good idea to put that into the server as well. T-SQL stored procedures that have massive amounts a non-dataset related code like encryption, conversions and extensive string manipulations could probably benefit from being completely or partially turned into managed CLR functions.

    If you on the other hand are writing classical dataset manipulation and selection procedures, then T-SQL is a language that is highly optimized and specifically designed for just that purpose. You should keep in mind that managed stored procedures still use T-SQL to interact with the relational database engine; look at some code samples!

    If you take a step back, you will see that you are making a decision about when it makes sense to utilize the database server processor over the application server processor. Clearly, application servers are a lot cheaper and usually a lot easier to scale out. At the end of the day, in any well designed distributed architecture, the database server is going to be your bottleneck. It would probably make sense to keep whatever processing you can away from that precious resource.

    However, if you are using an algorithm to determine what records to return to the client, and you expect that it may severely limit the amount of records returned to the client, then it probably makes sense to put it on the database server. Returning 2GB of data to the application server, and then filtering away 98% before returning it to the client may be a massive waste of resources. You’ll have to make an informed tradeoff decision.

    There are no absolute rules, but you will need to evaluate every single case for yourself. My advice is to stick with the way you’ve been writing applications with SQL Server 2000 and keep the T-SQL stored procedures the way they are. At least then you will know that whenever you utilize managed code in the SQL Server, you’ve made a conscious tradeoff rather then blindly following the ever popular anti T-SQL movement. Regarding business logic, keep it on your application tier where it has been living so happily over the last few years. Once again, if you do decide to move it to the SQL Server make sure it you’ve made a well informed decision that works with both your application and your business requirements.

    Leave your defaults the way they are; it’s an evolution not a revolution.

    Comments [0] | | #