review...

Signed-off-by: Alex A. Naanou <alex.nanou@gmail.com>
This commit is contained in:
Alex A. Naanou 2022-07-10 15:38:56 +03:00
parent 00d2f699e5
commit 4df54db767

View File

@ -1,6 +1,15 @@
/********************************************************************** /**********************************************************************
* *
* *
*
* Architecture:
* store
*
* page
* renderer
*
*
*
* XXX might be a good idea to try signature based security: * XXX might be a good idea to try signature based security:
* - sign changes * - sign changes
* - sign sync session * - sign sync session
@ -75,6 +84,8 @@ module.path = {
'NotFound', 'NotFound',
], ],
// Default alternate search locations...
//
// NOTE: if a path here is relative it is also searched relative to // NOTE: if a path here is relative it is also searched relative to
// the target path. // the target path.
SEARCH_PATHS: [ SEARCH_PATHS: [
@ -83,6 +94,12 @@ module.path = {
'/System', '/System',
], ],
// Path utils...
//
// Path can be in one of two formats:
// string
// array
//
// NOTE: trailing/leading '/' are represented by '' at end/start of // NOTE: trailing/leading '/' are represented by '' at end/start of
// path list... // path list...
normalize: function(path='.', format='auto'){ normalize: function(path='.', format='auto'){
@ -229,7 +246,16 @@ module.path = {
// .load(..) // .load(..)
// //
// //
// NOTE: store keys must be normalized... // NOTE: store keys must be normalized to avoid conditions where two
// forms of the same path exist at the same time...
//
//
// XXX potential architectural problems:
// - .paths()
// external index -- is this good???
// bottleneck??
// cache/index???
// ...can we avoid this??
// //
// XXX LEADING_SLASH should this be strict about leading '/' in paths??? // XXX LEADING_SLASH should this be strict about leading '/' in paths???
// ...this may lead to duplicate paths created -- '/a/b' and 'a/b' // ...this may lead to duplicate paths created -- '/a/b' and 'a/b'