Page Comparison

...

Channels implemented as IMultithreaded* are much more complex than normal IChannels with the same features. This is a serious problem in an open source project. It is a serious barrier to collaboration, and this reason alone is enough to warrant deprecation.

IMultithreaded re-invents Statics

...

There are no important advantages of IMultithreaded* to be had, and there are real costs of implementing this interface. It is clear that we should discourage implementation of channels as IMultithreaded*, and I think deprecating the interfaces is the clearest way to communicate this without ambiguity.

...

• Mark all IMultithreaded* interfaces in uPortal 2.4.-patches, 2.5-patches and 2.6 as deprecated.
  • IMultithreadedCacheable
  • IMultithreadedChannel
  • IMultithreadedCharacterChannel
  • IMultithreadedDirectResponse
  • IMultithreadedMimeResponse
  • IMultithreadedPrivileged

• Discourage use of these deprecated APIs
• Refactor the core channels to implement IChannel* .
  • These framework channels implement one of the IMultithreaded* interfaces:
    • CGroupsManager
    • CPortletAdapter
    • CWebProxy
    • CApplet
    • CGenericXSLT
    • CImage
    • CInlineFrame
    • CPersonAttributes
• Adopt a policy that no new channels implementing IMultithreaded*will be accepted into the framework (uPortal source tree)
• Propose a presentation for JA-SIG Vancouver conference "Why IMultithreaded is Deprecated and How to Refactor Your Channels away from IMultithreaded"