Monolithic file solution vs. Multiple file solution
Reasons to split up files:
- big size
  when is to big?
  how long does the backup take? too long?
- corruption
- reporting: high transaction rate/warehousing
- different user groups: more granularity in account order: web users / accountants
- API links: separate file, even separate server? transactions
- FMGo -> platform
  FMGo does not have link to 'desktop' files, but vice versa the desktop can have connection to FMGo
  -> performance!



Drawbacks:
- accounts -> oAuth/external accounts
- sync





To store or not to store?
- queries -> stored
- network performance: unstored can be faster when slow network because it is evaluated on the client
- both: for example stock information
- reporting: separate logic for data warehouse


Loading speed of records
- when a record is loaded its loading all stored data in that record
  --> split up into one-to-one tables
- storing large text/json/html file as external container


What when a lot of people want to see the same value list???
-> make it stored somehow?







PSOS with Callback
- feedback for server side scripts: long report -> feedback to user
- we could split complicated tasks in multiple tasks with callbacks ( ask Peter )
- error trapping on the server: return that error to the user
- listener on the server for every user to create messenger system? (wise???)


- not fail safe for now! what if a client is not connected anymore?
- does a looped script get kicked out when the user logs out?

- user session ( what is a user? ) message queue system
- MBS can do OS notification messages ( after PSOS is done ) seems safe

- works on WebDirect :-)

- strange behaviour of get(scriptparameter) during tests: see example file




Audit logging
- one more thing audit log solution
- MBS: function ( backend ) not tight to one particular layout
  possible to have seperate files to store that data
- get(modifiedfields)
- OnWindwoTransaction script trigger ( Vince Menano session )



Naming convention for Styles:
- Claus Lavendt: thebrainbasket.com
- minimise the amount of styles
- it helps having a template/style layout
- when swapping themes, it only works when the second one is a duplicate of the first one???
- is it possible to switch between dark and light theme easily?
  in this case we could just duplicate a layout and switch the theme.
- don't touch the default style (why? ask Claus)

see naming convention BrainBasket/SquareMoon


Where is my FMP file when I delete it on Mac??? 
( I'm still able to work on it, as long as I don't close it...)