Changes

Jump to navigation Jump to search
no edit summary
Line 52: Line 52:  
* Only Con: very new, we are all rookies.
 
* Only Con: very new, we are all rookies.
   −
Data access considerations
+
= Data access considerations =
Except for SOLID, there seems to be no easy way to transfer locally saved content from one browser or computer to another.
+
* Except for SOLID, there seems to be no easy way to transfer locally saved content from one browser or computer to another.
 
This means it would be useful to give the user the option to convert anonymous client data into server backed registration data, or rather, just use SOLID.
 
This means it would be useful to give the user the option to convert anonymous client data into server backed registration data, or rather, just use SOLID.
As our predicted volume of used data fields will probably stay in double digits, asynch or synch requests should not make a big difference in performance, however, in general it is good practice not accessing any local data until it is to be read or wrote. Also good practice to read local data into RAM/some js object once it is necessary, and use it from there then on, and only touching the local copy of data when writing into it.
+
* As our predicted volume of used data fields will probably stay in double digits, asynch or synch requests should not make a big difference in performance, however, in general it is good practice not accessing any local data until it is to be read or wrote. Also good practice to read local data into RAM/some js object once it is necessary, and use it from there then on, and only touching the local copy of data when writing into it.
Anonymous user

Navigation menu