Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28488

Add BlobProvider.supportsSync to avoid relying on BinaryManager for sync tests

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.10-HF21, 11.1, 2021.0
    • Component/s: BlobManager
    • Tags:
    • Impact type:
      API change
    • Upgrade notes:
      Hide

      New API: BlobProvider.supportsSync()

      Sync refers to the fact that a blob from this provider may be synced with a remote system (like Nuxeo Drive) or with a process that updates things in the blob (like Binary Metadata or WOPI).

      Show
      New API: BlobProvider.supportsSync() Sync refers to the fact that a blob from this provider may be synced with a remote system (like Nuxeo Drive) or with a process that updates things in the blob (like Binary Metadata or WOPI).
    • Story Points:
      2

      Description

      Various areas of the code test for synchronizability of a blob by checking blobProvider.supportsUserUpdate() && blobProvider.getBinaryManager() != null but the binaryManager check is an implementation detail which we want to get rid of.

      -> Introduce a separate BlobProvider.supportsSync method.

        Attachments

          Issue Links

          is required by

          New Feature - A new feature of the product, which has yet to be developed. NXP-28276 Refactor blob providers infrastructure for more flexibility

          • Major - Major loss of function.
          • Resolved

            Activity

              People

              • Assignee:
                fguillaume Florent Guillaume
                Reporter:
                fguillaume Florent Guillaume
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h