I'd suggest going with a JCR (JSR-170, JSR-283) [1] based solution (jackrabbit or day CRX) and a framework on top of that (for example apache sling) [2] or any of the CMS systems that are built on top of JCR (for example magnolia or day CQ5) [3].
- they implement security - storage is hierarchical, node level security, also with table style sql access - they take care of most web things like security, caching - they can cluster and scale - they let you focus on what you want to build and allow you to make it look pretty very easily (that's what a CMS is for, isn't it?) Ruben [1] http://jackrabbit.apache.org/ [2] http://sling.apache.org/site/index.html [3] http://www.magnnolia-cms.com/ On Mon, Aug 24, 2009 at 3:09 PM, Joshua Marinacci <[email protected]>wrote: > > * implement authentication, securely, over https > * create a user account database or hook into another one, along with > account creation / password change, maintenance tools, etc. > * handle fail over to other instances, including session affinity > * persist the storage to disk in a threadsafe and reliable manner, > possibly setting up my own sql db and jdbc connections. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
