I don't have any major objections. The need is obvious, we can quibble over the details later.
On Thu, Sep 25, 2008 at 1:19 PM, Brian Eaton <[EMAIL PROTECTED]> wrote: > On Thu, Sep 25, 2008 at 11:46 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > Again, though, we could always re-invent per-container configuration for > the > > umpteenth time that this discussion has come up, but we'll just come back > to > > the same conclusion. We've proven time and time again that per container > > configuration is necessary because many implementations need to support > more > > than one container in their deployment. > > Yep, I agree. I'd like to see somebody who works on the social-api > ack that this is the right thing to do before I check in a new > dependency. >
