Hey Blake - On Jan 30, 2008 3:57 PM, Blake Sullivan <[EMAIL PROTECTED]> wrote:
> I believe that we do want to do this, but we can hold off until we have > concrete needs unless the synchronization is actually killing our > performance on the Servlet Container implementations that we need to run on. Sounds good. > The issue for the Servlet implementations with moving over is that if code > is currently relying on the implementations performing their synchronization > for compound operations on the publicly accessible objects, the > implementations can't change to ConcurrentHashMap without breaking this > code. Okay, I am confused... Since the ServletContext's attribute Map is not a publicly accessible object (only access is through get/setAttribute()), can't the change be made transparently to app developers? Andy
