Just came across this .NET Security Blog that has been around for ages – neat! Subscribed.
I read this post by Savas Parastatidis which pointed to this paper on “Rethinking the Java SOAP Stack”. I was curious because I used one of the earlier SOAP stacks for Java from IBM before it went over to the Apache Foundation for further development, but I had managed to find myself in .NET land by the time Sun came around and really started supporting SOAP as a technology.
Its kind of amusing to see our Java cousins struggling with the same kinds of things that we do in the .NET space especially around what they called “O/X mapping”, a play on acronyms(?) with the familiar O/R mapping problem. From this paper it looks like they are going to move into angle brackets territory to solve the issue.
I thought this was an interesting approach because if you look at Indigo and Service, Operation and DataContracts they are trying to abstract away XML so only those that really want to deal with it have to.
You take the high road, I’ll take the low road . . .
Greg Low, one of the local SQL gurus has just launched a podcast targeted at the SQL community. I was fortunate enough to get a bit of a sneak preview at this and I really enjoyed it. For the inaugural show he has a chat with Kalen Delaney. Kalen is a SQL Server MVP like Greg and between the both of them it was great to cover some some of the SQL Server futures like Yukon (SQL Server 2005) but also some history with SQL Server.
Great work Greg! Subscribed.
I’ve posted quite a bit this month with a fairly reasonable mix of technical and non technical posts. I decided to plot my posting habits since I started my blog. There was a definate upwards trend at the tail end last year with a spike over January, I wonder what events in my life change my posting rate.
No, not the site – some of the responses. Darren posted up this one worder which pointed to an issue he raised with IBF and VS.NET 2003 on the Product Feedback Center site which is part of the MSDN lab. After five days of back and forth between the guys at Microsoft it was resolved as Not Reproduced.
Now – what annoys me isn’t the fact that the guys couldn’t investigate and fix the issue, its the fact they they didn’t forward this piece of feedback from an MVP and one of the few people who know about IBF (on the planet) to the Microsoft Office team to address.