PhotArk Gallery Interview

Apache PhotArk: ‘a complete open source photo gallery application.’

Jessica Thornsby

Apache PhotArk will be a complete open source photo gallery application.

Last week, the Apache PhotArk team released Apache PhotArk M3-incubating, an early release of the open source photo gallery application. In this interview, JAXenter speaks to contributor Luciano Resende, about what we can expect from this Apache project……

JAXenter: What is the Apache PhotArk project?

Luciano Resende: Apache PhotArk will be a complete open source photo gallery application including a content repository for the images, a display piece, an access control layer, and upload capabilities.

JAXenter: What functionality is currently available?

Luciano Resende: Apache PhotArk supports a standalone deployment in a JavaEE Application Server such as Apache Tomcat, or a cloud deployment as a Google AppEngine application. It allows users to create albums and upload pictures with the ability to protect it via a granular access control. It also allows subscription to external albums such as Picasa and Flickr, allowing users to aggregate these external albums in one central location.

JAXenter: What’s on your ‘wish list’ for the project, moving forward?

Luciano Resende: The Apache PhotArk community is discussing the following items as part of its roadmap :

– Make PhotArk more social, and integrate with other social networks such as Facebook.
– Expand album subscriptions to support other photo sharing sites.
– Enhance Google AppEngine feature set, aiming feature party with PhotArk standalone deployment.
– Provide a REST API and a Javascript Client API

JAXenter: What technologies are at work, in Apache PhotArk?

Luciano Resende: Apache Photark is currently designed as a Web 2.0 application that can be deployed to a Java EE Application Server such as Apache Tomcat. The PhotArk components are defined using the SCA programming model and Apache Tuscany is used as the SCA Runtime. There is also integration with Apache JackRabbit for the Content Repository. On the client side, it uses DHTML and Dojo 1.5 to build a rich user experience.

Inline Feedbacks
View all comments