Changes between Version 16 and Version 17 of NextforHMS

Timestamp:

01/28/10 18:21:48 (15 years ago)

Author:

Dominic König

Comment:

--

NextforHMS

@@ -62 +62 @@
  - If the main concern is keeping certain data away from the general public, and we are time crunched, then a generic anonymous / read-only / read-write structure is fine...but this makes it very hard to change in the future. 
 
- - There is an more optimal method of assigning flags to users, which indicate what capabilities they are allowed, as opposed to role-based (nursix thinks: opposed? individual user-based ACL too complex for disaster response, role-based ACL is a proven good solution, and you can always add one "role" per user and thus establish an individual ACL)
+ - There is an more optimal method of assigning flags to users, which indicate what capabilities they are allowed, as opposed to role-based (nursix thinks: role-based ACL is a proven good solution, implemented by the web2py framework, so nothing we have to develop, and you can always add one "role" per user and thus establish an individual ACL)
 
  - we've already leaked a good quantity of data to various search engines and blogs and whatnot. I imagine this current push is to secure future data we capture.