WCSFBuilder

Topics: Web Client Software Factory
Dec 5, 2006 at 7:55 AM
Can anyone explain why the need to a custom Builder?
Coordinator
Dec 5, 2006 at 5:17 PM
This is a great question.

In our development and testing of the WCSF, we ran into an issue with the "default" Builder class causing a lot (and I do mean a lot) of thread contentions because of the very coarse-grained locking strategy. We had tested OB on server environments for Enterprise Library, but we are using OB in a completely different way in WCSF which surfaced this issue. In BuilderBase, the locking policy locked if there was a chance of touching anything. We created a new BuilderBase that did not have this very pessimistic policy, and instead moved the locking to the new WCSFCreationStrategy instead. This removed the bottleneck and the thread contentions that were occurring.

Eventually, we would like to merge this improvement back into the Object Builder source code. However, until we have a chance to do a complete test run on the entire OB tree considering all use cases, we are going to ship this as an extension. As a guess, this will happen in the Enterprise Library 3.0 timeframe, however the decision on when will be up to the Enterprise Library team (so don't consider this a promise).