Package ch.autumo.beetroot.server.modules
package ch.autumo.beetroot.server.modules
Dispatcher interfaces for creating your own distributed dispatchers (modules) for the beetRoot client-server framework.
Basically, you create a factory that checks whether a call is made from a remote location (e.g. in a web container) or locally (within the beetRoot server). This can be determined by calling
If a servlet context is present, you call from a web container, and in this case your factory returns a remote implementation that is part of the distributed module and that uses the
If there is NO servlet context (null), the calls are made within the beetRoot server. In this case, the factory provides a local implementation that is part of the distributed module. The dispatcher implementation itself always calls the dispatcher implementation itself always calls the local implementation, and the dispatcher itself is automatically involved when remote calls are made via the remote implementation.
All calls are secured either by SHA3 or SLL, depending on the configuration. For successful dispatching on the server side, you must register your dispatcher implementations in the application configuration
Basically, you create a factory that checks whether a call is made from a remote location (e.g. in a web container) or locally (within the beetRoot server). This can be determined by calling
BeetRootConfigurationManager.getInstance().getServletContext();.
If a servlet context is present, you call from a web container, and in this case your factory returns a remote implementation that is part of the distributed module and that uses the
ClientCommunicator
or the ClientFileTransfer to call the server.
If there is NO servlet context (null), the calls are made within the beetRoot server. In this case, the factory provides a local implementation that is part of the distributed module. The dispatcher implementation itself always calls the dispatcher implementation itself always calls the local implementation, and the dispatcher itself is automatically involved when remote calls are made via the remote implementation.
All calls are secured either by SHA3 or SLL, depending on the configuration. For successful dispatching on the server side, you must register your dispatcher implementations in the application configuration
cfg/beetroot.cfg;
see keys dispatcher_*.-
InterfacesClassDescriptionDispatcher for server commands received server-side; every remote component must implement a dispatcher.File storage interface.