No co-location exploitation. Scaleable and replicable components. Parse headers into contexts of attribute value pairs. All components in their architecture have IDL interfaces so they can run in different environments. You need different TCP components because they must be retargetable.
Partners can extend the architecture via replacing modules and server side scripting.
Might have reached a limit in componentry. The humble stream still as legs. The component approach is best. Context is hard - seems to be an optimization problem. CM, management, alerts is a big resource sink.