Changes between Version 1 and Version 2 of CryptoPlugin/Dev/DbSchema


Ignore:
Timestamp:
Jun 25, 2012, 9:57:43 PM (2 years ago)
Author:
hasienda
Comment:

add more explanations around choice of session_attribute storage

Legend:

Unmodified
Added
Removed
Modified
  • CryptoPlugin/Dev/DbSchema

    v1 v2  
    55
    66== Common "parasite" storage ==
    7 Entries in `session_attribute` seem like a perfect match for the first requirement.
     7Session attributes are easily accessible related on a client sessions base in Trac's Request object (`req.session`), without the need for a direct db connection.
     8So entries in Trac db table `session_attribute` seem like a perfect match for the first requirement - no need for an own db table here.
    89I've chosen the following dedicated names for related association types:
    910 * 'sign_key'
    1011 * 'crypt_key'
    1112 * 'auth_key' (''future'')
     13Their meaning should be easily guessable from these names.
    1214
    1315== Dedicated "private" storage ==
     
    2224  * version,
    2325  * fragment,
    24  i* key_id,
     26i * key_id,
    2527    signature
    26  i  time,
     28i   time,
    2729
    28  * primary key
    29  i has dedicated index:
     30Legend:
     31  * primary key
     32i   has dedicated index
    3033}}}
    3134