Items that need to
...
Item
...
Description
...
Type
...
be stored in an org.osid.OsidContext object
There is a unique OsidContext object for each user. The OsidContext object gets loaded into the RepositoryManager when a user starts a new "search session" (selecting sources, conducting a search, paging through results, selecting certain results, etc.). The RepositoryManager will then "know" the user throughout the user's session in the system.
Key | Description | Type |
|---|---|---|
| identifies which repository belongs to the user of this OsidContext | long alpha-numeric string |
| necessary to identify a specific user and allow that user access to X-Server services | long alpha-numeric string |
| identifies a result set created by submitting a query with the /wiki/spaces/SLIB/pages/2921168923 command. This number is necessary for asynchronous searches, retrieving results and pagination | short numeric string |
new session flag | a flag indicating whether the user has logged in or not | boolean variable |
selected search sources | user-selected search sources used for multiple queries | list of alpha-numeric |
short string ("true"/"false") |
Issues
- How do we know when a user's session is done? This is up to the consumer. In our case (using Servlets), we can choose when to invalidate a session: a timeout & when the search dialog is closed.
- Will the metasearch engine support multiple users logged on at once? Yes.