[CADIHash.h Index] [CADIHash.h Hierarchy]
This structure handles the sessions; by this, it encapsulates the current state of the server More...
#include <../libInvertedFile/include/CSessionManager.h>
Inherits: CAlgorithmCollection
This structure handles the sessions; by this, it encapsulates the current state of the server. Basically, it hands all requests through to the right sessions. It also handles the generation of new sessions etc.. In short, it is the configuration manager.
Together with CCommunicationHandler, this is the structure is the most affected with all the business about changing and improving MRML. It contains now quite a lot of entropic code which needs to be cleaned up.
NOTE: I (WM) guess, that the outcome will be something like a new ConfigurationManager Class, which contains a CSessionManager (which will manage only sessions) a CAccessorCollection, and a CAlgorithmCollection. It will contain quite a fat interface to hand through to them.
The session manager slurps in two XML files and generates out of this its initial state.
this CSessionManager has all the information to make a query structure.
Initialization: read from a stream
Write into a stream
to be used by the Interface. Not yet implemented.
to be used by the Interface. Not yet implemented.
to be used by the Interface.
to be used by the Interface.
VIF This function looks for a CSession with CSession::mSessionID==inSessionID and hands through the rest of the parameter list to CSession::query.
retrieving the URLs of all images (for generating distance matrices)
retrieving the IDs of all images (for generating distance matrices)
set the algorithm used in this sessionit will also lead to a new construction of the query.
We have to perform some comparisons here present version is probably a HACK
making a new session and returning its ID
Set the name of the current session.
turn this into a part of the welcome message THIS CODE IS TO LEAVE SOON
The sessions for one user only.
inUser | the name of the user for which we want the session names. |
isPrivate | send internal configuration information along? (distinction between messages for internet and config files) |
The sessions for everybody known to the system
this is almost the complete shandshake message
Get the property sheet of the algorithm with ID inAlgorithmID.We look for the attribute cui-property-sheet-id in the algorithm. If this exsists, we look for the right property sheet id in the CPropertySheetList.
Building a property sheet listI consider building a list on a call by call basis as tedious. So what I do is: I first build a tree, and then I break down this tree into our list.
This function makes a new tree
This function gets us the current property sheet subtree.
This function does the actual breaking down into a CPropertySheetList.
This function probably will quite soon be removed from this class,
This function probably will quite soon be removed from this class,
The accessor collection is needed for constructing queries
These are the building blocks of the property sheets to be generated by *this.
The subtree from which the mPropertySheets
Documentation generated by muellerw@pc7170 on Son Okt 8 16:04:40 CEST 2000 | Kdoc |