[
https://issues.apache.org/jira/browse/PHOTARK-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Pradeep updated PHOTARK-42:
--------------------------------
Attachment: photark-jcr.patch
Have refactored the JCR Gallery service to follow REST style, need your
feedback/comment on the same.
I still have to write JUNIT test cases for the same and make sure it is
complete, but before that i want to know if the appraoch taken is right.
Please provide your suggestion/comments to make sure i have not missed out
anything.
Note: The patch should be applied for
https://svn.apache.org/repos/asf/incubator/photark/branches/photark-rest/photark-jcr
> Improve PhotArk services by refactoring current Services and Model Objects
> --------------------------------------------------------------------------
>
> Key: PHOTARK-42
> URL: https://issues.apache.org/jira/browse/PHOTARK-42
> 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 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
