Uploaded image for project: 'onedata'
  1. onedata
  2. VFS-1956

Redesign helper contexts

XMLWordPrintable

      • Icon: Improvement Improvement
      • Resolution: Fixed
      • Icon: Major Major
      • None
      • None
      • helpers
      • None
      • Sprint 86, Sprint 87, Sprint 88, After DI4R'2016 Sprint 89
      • 8

        In current design, we have two elements for a helper operation: a helper, which is specific to a storage, and a helper context which is specific to

        {file, helper}

        .

        There are several problems with the design:

        • Helper for a storage can change on-the-fly, requiring us to detect and convert the context on-the-fly as well (and we don't have any data needed to create the new context).
        • The context is converted every time a context from a different helper is used
        • Some logic is ill-suited for either level (file or storage), e.g. a per-user connection in Ceph shouldn't be per-file (in helper context) nor per-storage (in helper)
        • The interface is dynamic to the point of being silly (e.g. everything is passed as <string,string> map)

        Some thoughts:

        • Decouple context from helper
        • Introduce another, user-level context

                  plgkzemek kremek (Inactive)
                  plgkzemek kremek (Inactive)
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                    Created:
                    Updated:
                    Resolved: