You raise a valid point here.
I should have noted that I don't have ANY persistency story because this whole architecture is only for reading objects.
It's purely for displaying data, I don't have write access to the database at all. So for me the #1 priority was to read fast.

It made sense to have the Repository be a singleton since I use a caching layer above it as I wrote about here:
http://www.tigraine.at/2009/05/12/kaerntenat-ca… (yes, just recently, had some NDA issues before).

So anyway there will only be one initialization of the repository since the cache holds only one reference to the repository.

Sorry for the confusion.
greetings Daniel

I read your original post for InjectableDataContext, http://www.tigraine.at/2009/04/10/how-to-make-a…, and assumed you would've implemented you UserRepository differently using Windsor.

I don't follow this logic, “Now, the logical thing to do in my IoC configuration was to have the repositories be singletons, and so every repository has one datacontext attached to it.” Why would you want your repositories to be singletons? DataContext is not designed to be used concurrently by multiple threads. I would've assumed your repository constructor would've created the DataClassesDataContext instance (or the InjectableDataContext instance) via the Windsor container. This should allow you to set the windsor component lifestyle to Transient, which would cause a new instance of DataClassesDataContext to be created on a per request basis.

# public UserRepository()
# {
# this.context = container.Resolve<DataClassesDataContext>();
# }

This way you could still use all of the CRUD/Transaction niceness of LinqToSql because each Repository would run with its own context and you wouldn't have multiple threads attempting to use the same context.

If you were using your Repository as a singleton I don't know how you could possibly get methods like these to work with your context:

//Insert/Delete
public void Add( BlogUser user) {
context.Users.InsertOnSubmit( user);
}

public void Delete( BlogUser user) {
context.Users.DeleteOnSubmit( user);
}

//Persistence
public void Save()
{
context.SubmitChanges();
}