As mentioned, I'm not entirely certain whether or not going to all this trouble is worth the effort, particularly when just using the BindToListControl method (since something like that can easily be implemented without strong-typing).  It may be that only hard-core middle-tier purists will appreciate the architecture; however it does illustrate (albeit quietly) the ease with which you can bind custom business object collections to data controls, which I think is a really great feature of .NET.

It also offers, as you might expect, a fairly decent separation of UI from the data.  This could easily be abstracted to use other data sources using the IDb interfaces.  And it would not be hard to offer simpler parameter addition if it's found that the event handler option is not usable.  It also lends itself easily to plopping the collection into a cache of some sort for reuse and ease of binding.

Again, let me know what you think, either by feedback, rating, or at the related post on my blog.  I appreciate any insight on how this concept might be expanded or modified to be more usable in day-to-day application development.