| org.jasig.portal.IPrivilegedChannel
All known Subclasses: org.jasig.portal.MultithreadedPrivilegedMimeResponseCharacterChannelAdapter, org.jasig.portal.channels.CSecureInfo, org.jasig.portal.channels.CLogin, org.jasig.portal.channels.DLMUserPreferences.BaseState, org.jasig.portal.channels.jsp.Channel, org.jasig.portal.MultithreadedPrivilegedCacheableChannelAdapter, org.jasig.portal.MultithreadedPrivilegedCacheableMimeResponseCharacterChannelAdapter, org.jasig.portal.channels.DLMUserPreferences.CUserPreferences, org.jasig.portal.channels.error.CError, org.jasig.portal.channels.CSnoop, org.jasig.portal.channels.UserPreferences.BaseState, org.jasig.portal.channels.UserPreferences.CUserPreferences, org.jasig.portal.MultithreadedPrivilegedCharacterChannelAdapter, org.jasig.portal.channels.CError, org.jasig.portal.MultithreadedPrivilegedCacheableCharacterChannelAdapter, org.jasig.portal.MultithreadedPrivilegedMimeResponseChannelAdapter, org.jasig.portal.MultithreadedPrivilegedCacheableMimeResponseChannelAdapter, org.jasig.portal.MultithreadedPrivilegedChannelAdapter,
| IPrivilegedChannel | | public interface IPrivilegedChannel extends IChannel,IPrivileged(Code) | | Channels implementing this interface are considered "privileged" because
they will have access to internal portal control structures such as the
HttpServletRequest, HttpServletReponse, and UserPreferencesManager. IPrivilegedChannel
is intended for channels that are integral to the framework such as those that
manage user preferences, channel publishing, and channel subscription.
IPrivilegedChannel is NOT intended for "normal" channels. Channels
should normally implement
IChannel .
Portal administrators should only allow publishing/subscibing of channels
implementing IPrivilegedChannel if the following are true:
- The channel is an integral part of the uPortal framework, e.g.
org.jasig.portal.channels.CLogin .
- The channel is well-understood and will not cause harm. An understanding of the
portal architecture is necessary to determine if this is true.
- There is no way to implement the channel as an IChannel because access to
internal structures is absolutely necessary.
author:
Peter Kharchenko, pkharchenko@interactivebusiness.com
version:
$Revision: 34818 $
See Also: IChannel
See Also: PortalControlStructures |
|
|