Andres Aguiar's Weblog

ADO.NET does not specify a standard way to set parameter markers in a SQL statement. For example, if you use the SQL Server Data Provider, you have to write:

When less is more [IUnknown.com: John Lam's weblog on software developer]

James Strachan agreed with my post about domain data, and made some suggestions for the Java world.

Chris did not agree with my comments about Java and Open Source projects. Niel got my point.

Rickard Öberg did an in depth revision of Middleware Company's Pet Shop application did not like what he saw.

I tend to rely more on the Transaction Script model. The biggest problem with Transaction Scripts is the duplication of logic. But through copious amounts of refactoring, I can keep that at a minimum. Transaction Scripts allow me to treat one page as an application. It knows how to get the data it wants and how to display it. That's it. It doesn't use an object model that might have to make use of 4 other objects in order to get all the data you want to display.

There is a new benchmark in the Java side for the Pet Shop application. It was made by 'The middleware company', the company behind TheServerSide, and this time they tuned it for performance, and it was much faster than the original Sun implementation.

Tim Ewald makes the case against SOAP Section 5 Encoding which the WSI-I was very smart to exclude and prohibit from their basic profile [Sam Gentile's Weblog]