As per meeting 16.01.24 it would be advisable to expand the Rest-API to reduce message-size for/and performance. Priority-ordered from high to low:
- /fact/list: add feature to allow requesting of just static facts (created at server startup/archives) and dynamic facts (created over Rest-API)
- repair /scroll/list[all]: broken since new relational database
- exclude helper functions of scrolls during dynamic/apply requests, but retain ability to access them (e.g. "theory funcs" in http://mathhub.info/FrameIT/frameworld?RiverScroll)
- add ability to remove facts from server
- add ability to create and close sessions?
As per meeting 16.01.24 it would be advisable to expand the Rest-API to reduce message-size for/and performance. Priority-ordered from high to low: