---

	Interface	Description
	IArgumentPreprocessor
	IComponent	Interface for components remote proxies
	IContextManager	Interface for context managers
	IEntity	Interface for Tide managed entities In general it will be implemented by entities generated by gas3.
	IEntityManager	IEntityManager is the interface for entity management (!) It is implemented by the Tide context
	IEntityRef	Holds a compact reference to an entity
	IExceptionHandler	Interface for exception handlers An exception handler should tell which ErrorMessage it handles and do some action when the accepted error happens
	IExtendedExceptionHandler	Interface for extended exception handlers An exception handler should tell which ErrorMessage it handles and do some action when the accepted error happens Extended exception handlers can get the origin TideFaultEvent Note: this should be deprecated in the next major release and merged in the standard IExceptionHandler interface
	IIdentity	Interface for identity component
	IMessageInterceptor
	ITideMergeResponder	ITideMergeResponder defines an interface for extended remote call responders TideResponder is sufficient for most use cases but implementing this allows a more typesafe implementation if needed
	ITideModule	ITideModule defines the basic interface for Tide modules Tide modules just have to implement the init method which can register components, exception handlers...
	ITidePlugin	ITidePlugin defines the basic interface for Tide plugins Tide plugins can be more deeply integrated in the Tide container than simple components and are involved in the security lifecycle
	ITideResponder	ITideResponder defines an interface for extended remote call responders TideResponder is sufficient for most use cases but implementing this allows a more typesafe implementation if needed

	Class	Description
	BaseContext	BaseContext is the base implementation of the component/entity container context It is mostly an abstract class that is not exposed directly.
	Component	Component is the default implementation of remote proxies It can handle deferred property set/get on proxies
	Context	Default Context implementation when using Tide standalone
	DefaultExceptionHandler	Default exception handler that just displays the fault in an Alert
	InvalidContextError	Exception thrown when trying to do some action on a context that is marked as finished
	Subcontext	Subcontext is a simple proxy that owns 'real' components in a particular context namespace
	Tide	Tide is the base implementation of the Tide application manager singleton
	TideAsync	Plugin for managing asynchronous events with a Gravity Consumer
	TideMessage	TideMessage is a simple status message object with a severity and text It is similar to the JBoss Seam StatusMessage class or the JSF FacesMessages In general it is used to get messages from the server but messages can also be added locally
	TideResponder	TideResponder defines a simple responder for remote calls It allows to keep a token object between the call and the result/fault handler It also allows to add many result/fault handlers that will all be triggered by the origin call