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

Refactor SPI and Core for API performance

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0
    • Component/s: None
    • Labels:

      Description

      The last refactoring for version/content has left an issue:
      The SPI content contains an array of locations. This is not synced with public API yet with "ugly" consequences: If PAPI impl wants to fetch locations for a content info it has to load the whole content.
      (e.g. content is then loaded unnecessarily on loading trash items)
      In PAPI we have an extra method loadLocationsForContent.

      Refactoring Steps:

      • Remove locations from SPI Content
      • Add a similar method to location handler:
        getLocationsForContent($contentId, $rootLocationId)
      • reimplement loadLocationsForContent in PAPI
      • fix all other Implementations using the loadContent method for fetching locations

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            bertrand.dunogier@ez.no Bertrand Dunogier
            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 - 2 days, 3 hours
                2d 3h