I have started working on some design changes for PhotArk, trying to
separate the model objects from actual component services. I have
updated the "Architecture Guide" [1] with some of these changes and
the ideas I have in mind. In summary, I guess I want to apply the
following changes :

- Separate PhotArk model from Service Implementation (see Model UML at [1])
- Remove any "behavior" from the current model Objects, make them
light way (e.g Images only have image URL instead of "image file
stream")
- Have all Components as SCA Components, and leave the life cycle
management of these components handled by the Tuscany Runtime (see
Composition diagram at [1])

Please let me know your thoughts, and let me know if you have questions.

[1] 
http://cwiki.apache.org/confluence/display/PHOTARK/PhotArk+Architecture+Guide

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Reply via email to