Changes between Version 2 and Version 3 of Ticket #1552


Ignore:
Timestamp:
Dec 9, 2010, 10:45:58 AM (13 years ago)
Author:
brucedechant
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1552 – Description

    v2 v3  
    55The solution to address this issue is to remove the bottleneck of all session information being funneled through a single session repository. By having a session repository per created session the bottleneck is removed with the only side effect being an increase in the memory used by the server.
    66
    7 To allow for better control over the number of created session repositories a new serverconfi.ini property “!SessionRepositoriesLimit” should be added to restrict this as needed.
     7To allow for better control over the number of created session repositories a new serverconfi.ini property should be added to allow restricting this as needed. Also, in order to be more flexible a new serverconfig.ini property should be added to allow using the old repository solution or the new solution.
    88
    9 Also, in order to be more flexible a new serverconfig.ini property "!SessionRepositoriesConfig" should be added to allow using the old "!SingleFile" repository or the new "!FilePerSession" solution.
    10 
    11 
     9{{{
     10[ResourceServiceProperties]
     11# SessionRepositoriesConfig        Sets whether to use a single file session
     12#                                  repository or a session repository file per session.
     13#                                       SingleFile or FilePerSession
     14# SessionRepositoriesLimit         The total number of active session files allowed.
     15#                                  This setting only works when FilePerSession
     16#                                  is used.
     17SessionRepositoriesConfig          = FilePerSession
     18SessionRepositoriesLimit           = 200
     19}}}