incubator-photark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luciano Resende (JIRA)" <>
Subject [jira] Commented: (PHOTARK-42) Improve PhotArk services by refactoring current Services and Model Objects
Date Thu, 10 Jun 2010 07:09:12 GMT


Luciano Resende commented on PHOTARK-42:

Thanks John Pradeep, partial patch applied.

> Improve PhotArk services by refactoring current Services and Model Objects
> --------------------------------------------------------------------------
>                 Key: PHOTARK-42
>                 URL:
>             Project: PhotArk
>          Issue Type: Improvement
>          Components: PhoatArk Services
>    Affects Versions: PhotArk M2
>            Reporter: Luciano Resende
>            Priority: Critical
>             Fix For: PhotArk M3
>         Attachments: photark-jcr.patch
> 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
> 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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message