Home | Trees | Indices | Help |
|
---|
|
Context passed to all servants.
server_id, communicator, and stop_event will be constructed by the top-level Server instance.
A context instance may also be configured to hold on to an internal session (ServiceFactoryPrx) and keep it alive.
This instance obeys the Resources API and calls sf.keepAlive(None) on every check call, but does nothing on cleanup. The sf instance must be manually cleaned as the final operation of a servant.
(Note: cleanup of the server context indicates server shutdown, so should be infrequent)
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from |
|
|||
Inherited from |
|
x.__init__(...) initializes x; see x.__class__.__doc__ for signature
|
|
Returns the ServiceFactoryPrx configured for the context if available. If the context was not configured for sessions, an ApiUsageException will be thrown: servants should know whether or not they were configured for sessions. See Servant(..., needs_session = True) Otherwise, if there is no ServiceFactoryPrx, an attempt will be made to create one if recreate == True. If the value is None or non can be recreated, an InternalException will be thrown. TODO : currently no arguments are provided for re-creating these, but also not in Servant.__init__
|
Calls getSession() but always returns True. This keeps the context available in the resources for later uses, and tries to re-establish a connection in case Blitz goes down. |
Does nothing. Context clean up must happen manually since later activities may want to reuse it. Servants using a server connection should cleanup the instance *after* Resources is cleaned up |
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Wed Jul 14 15:40:22 2010 | http://epydoc.sourceforge.net |