Skip to content

Caching of object artifacts and config #76

@sbcgua

Description

@sbcgua

Ideas from #72

  • Problem 1: the config is sent with each request
  • Problem 2: dependencies are sent in each request

Ideas:

  • Addressing just 1: Supposing that abaplint backend would be most probably private, we can store configs as key/value. Where key would be repo url (which is uniq enough) and value - the config. The assignment can be done from UI. So adding a new package at UI side would ping server side to check presence of the config and submit it if missing or changed
  • Addressing both: implement sessions. On SCI start, it requests (or generates UUID) a session key, and then server can store the cache for some period of time. Including config and dependencies ! Does SCI keeps same abap session between object to have singletons ? This can be a bit tricky but totally implementable

Maybe both can be implemented, because the actually solve a bit different nuances. E.g. storing configs may be useful to define a global corporate config like descussed in #72

@larshp @g-back

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions