Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-19920

Spec & prototype Cluster support on Binary File FieldTypes by using IO handler

    Details

    • Sprint:
      Stetind Sprint 1, Stetind Sprint 2, Stetind Sprint 3
    • Story Points:
      2

      Description

      Background:

      • IO handler and IO service was originally made to handle this, but it implied user of Public API needed to create the files first and then pass the resulting file value to a binary fieldType, this had usability as well as legacy integration problems (image, files and media files all have slightly different needs and is stored in separate tables)
      • In august binary filedTypes were fixed to work, however prior work was not reused, so the result is a fileService which does not know about cluster and is not a 100% good match for cluster

      TODO:

      • create a API\FieldType\FileService interface based on the best of IOService and Core\FieldType\FileService
        • Make sure it maps well with IOHandler, and make sure IOHandler maps well with what is available in 4.x cluster interface
          • Find a better way to expose image data (getMetaData), that can work with 4.x cluster
          • Change getFileSize to map well to stat api in 4.x cluster
          • Make sure it suits well for FieldType needs (as IOHandler / Service was originally ment for slightly different use case)
      • remove IOService
      • expose the new FileService via FieldTypeTools
      • Refactor binary FieldTypes to use it

      NOTE: Time limited to 2 days

        Issue Links

          Activity

          Hide
          André Rømcke added a comment -

          Closing as there will be a followup impl story.

          Show
          André Rømcke added a comment - Closing as there will be a followup impl story.

            People

            • Assignee:
              Unassigned
              Reporter:
              André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days, 2 hours Original Estimate - 2 days, 2 hours
                2d 2h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 6 hours, 46 minutes
                2d 6h 46m

                  Agile