incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "CaitrinProposal" by RolandWeber
Date Wed, 16 Jul 2008 09:31:01 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by RolandWeber:
http://wiki.apache.org/incubator/CaitrinProposal

The comment on the change is:
first set of changes, see mail on projects-at-incubator.apache.org

------------------------------------------------------------------------------
  If a picture tells a thousand words then a gallery of pictures tells an amazing story. 
It could tell this story as part of a larger web site, in a blog or on its own.  Unfortunately,
there exists no Java open source application to assist the community to tell this story. 
*Insert name here* will change that.
  
  There are many photo galleries that are written in PHP.  Each of these addresses a particular
need and many work well for their intended purpose.  However, there is not a photo gallery
that is written in Java.  As Web 2.0 continues to grow it only makes sense that the community
provide not only PHP but also Java applications to allow everyone the ability to publish their
own content.  Apache started down this road with Roller and can continue with *Insert name
here*.
+ 
+ 
  == Initial Goals ==
-  * Decide which pieces of code can be drawn from existing projects
+ 
+  * Create a prototype by drawing pieces from existing efforts
   * Recruit additional community members
  
-  *Finalize the Content Repository
+  * Finalize the Content Repository
-    * Use cases - capture ideas such as access control that might not make
+    * Use cases - capture ideas such as access control that might not make first drop
- first drop
     * Layout
     * Unit tests (simple drivers for loading, accessing, searching, etc.)
  
@@ -39, +41 @@

     * semantics
     * prototype implementation
  
-  * WS-
+  * Web service
     * Use cases - want to capture ideas for process (Ode) integration
     * WSDL Description
     * prototype
+ 
  === High Level Design ===
+ 
  There are still many questions that need to be answered regarding this application.  They
are all asked with their appropriate topic but summarized here:
  
   * Should the user management default be Apache Directory or a simple database?
+  * How will access control be implemented?
   * Will the Web service just provide data for machine to machine exchanges or will it default
to human readable?
   * Should the project impose a backend data storage mechanism and schema, or just WS/REST
interfaces suitable for pluggable frontends?
   * Should we use JCR or a (relational) Database?
@@ -54, +59 @@

  
  The photos and meta data will be exposed via a Web service.  During discussions on the lists
regarding how the code should be written, the one thing that no one seemed to be able to agree
on was how the photos should be displayed.  Some would like to see them in Flash, others AJAX,
still others as a JSP library.  Exposing the information as a Web service allows for each
of these display formats to be utilized.  Question: Will the Web service just provide data
for machine to machine exchanges or will it default to being human readable?  If it only provides
for machine to machine exchanges then a default option for display will need to be provided.
 We plan on looking at the Tuscany SCA implementation to facilitate the WS.
  
- The user management system will be based on JAAS.  It should be implemented in such a way
that it can also be flexible.  An end user should be able to integrate any existing user authentication
tool against it.  Question: should the default be Apache Directory or a simple database? 
User authorization will facilitate photos being marked as public (anyone), protected (invite
only), or private (just the owner).
+ The storage for all data will use Apache Jackrabbit and as logically follows Sling.  The
actual node and property structure has yet to be determined.  Questions: Should the project
impose a backend data storage mechanism and schema, or just WS/REST interfaces suitable for
pluggable frontends?  Should we use JCR or a (relational) Database?
  
- The storage for all data will use Apache Jackrabbit and as logically follows Sling.  The
actual node and property structure has yet to be determined.  Questions: Should the project
impose a backend data storage mechanism and schema, or just WS/REST interfaces suitable for
pluggable frontends?  Should we use JCR or a (relational) Database?
+ Access control should provide the option to mark photos as public (anyone), protected (invite
only), or private (just the owner). Options for managing the invites for each user are LDAP
or a simple database. Permission checking can be implemented in the backend as a Jackrabbit
AccessManager or in an application layer. Candidate technologies are JAAS and JSecurity, which
both allow for pluggable authentication.
+ 
  
  == Current Status ==
  There are 4 code bases that will be available to draw from when starting the project.  Currently,
due to a 
@@ -102, +108 @@

  === Orphaned Projects ===
  
  === Inexperience with Open Source ===
- Of the existing community, only one member has limited experience with open source.  She
is committed to learning the Apache Way.
+ 
+ The initiator of this proposal has limited experience with open source. She is committed
to learning the Apache Way. The other members of the community we currently see forming are
Apache PMCs or members.
+ 
  
  === Homogeneous Developers ===
  The current community grew out of a desire to see different pieces of technology put to
use and an interest in the problem space.  There is no single entity that is providing all
the developers for this project.

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message