Uploaded image for project: 'PhotArk'
  1. PhotArk
  2. PHOTARK-42

Improve PhotArk services by refactoring current Services and Model Objects

Add voteWatch issue
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • PhotArk M2
    • PhotArk M4
    • PhoatArk Services
    • None

    Description

      The current album service has grown out of control, and the client makes multiple calls to the service to retrieve multiple album information.
      We should start using more model/business objects, and stateless services that act on top of these objects.

      I'd like to propose we start defining Album as pure model/business objects that will have all album related info (e.g name, description, cover image url, etc) and same thing with Image.

      As for services, we should create a facade service to retrieve info in a more atomic way, e.g Gallery.getAlbum(albumName) retrieve a album model object with all info for the album at once. We might have a second operation to retrieve list of album images if we think it's too heavy to retrieve all at once....

      Once we have this, we can start looking into applying more RESt style APIs and revisit how we can start taking advantage of http caching to improve performance of the overall client/server experience.

      Attachments

        1. photark-jcr.patch
          17 kB
          John Pradeep

        Activity

          People

            Unassigned Unassigned
            lresende Luciano Resende

            Dates

              Created:
              Updated:

              Slack

                Issue deployment