Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
01/30/12 09:42:09 (12 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
accepted
- Property Cc jburel added
-
|
v9
|
v11
|
|
| 71 | 71 | * !TurboGears {{{@validate(), @expose(), etc.}}} (http://turbogears.org/2.0/docs/modules/tgdecorators.html) |
| 72 | 72 | * Pylons {{{@validate(), @jsonify(), etc.}}} (http://docs.pylonsproject.org/projects/pylons-webframework/en/latest/modules/decorators.html) |
| | 73 | |
| | 74 | = Shares & Sessions = |
| | 75 | |
| | 76 | Previous to 4.4, the creation of sessions for shares used the stored username/password to create a new session. Part of the refactoring described above will remove that stored username/password. However, it is not necessarily possible for a user to create a new session from an existing session (this is only allowed if the session is authenticated with a password). Nevertheless it is necessary to be able to activate a session for one user in one process without effecting the other processes that are currently using the same process. Josh and Chris have agreed that extending the `{"omero.group":"1"}` functionality to also support shares should simplify things greatly. Each method invocation, regardless of group or session, can pass a share setting essentially activating that share for the duration of the method call. This will take place as a part of #3529. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.14230 sec.)
