[opencms-dev] OpenCms in the future?

[Martin van den Bemt]

http://incubator.apache.org/jackrabbit/ ?

Mvgr,
Martin 

-----Oorspronkelijk bericht-----
Van: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] Namens Joe Desbonnet
Verzonden: donderdag 15 september 2005 16:45
Aan: The OpenCms mailing list
Onderwerp: Re: [opencms-dev] OpenCms in the future?

I wonder does it make sense to make a clean separation between the VFS and
the rest of OpenCms. If the API between the two is well defined then the VFS
could be worked on and experimented with in parallel with the higher layers
of OpenCms.

So projects like adding support for new databases, use of Hibernate, JSR 170
stuff etc could be worked on and informally distributed as alternative
implementations of a "vfs.jar" file.

Alkacon can then take the stuff that works and integrate it into the
'official' vfs.jar from time to time.

Any comments?

Joe.


On 9/15/05, Alexander Wallace <aw at avatartechnology.com> wrote:
> I guess i was late to the parade :), this is what i was talking about 
> in my previous emails... I appologize...
> 
> I think this is a great idea!
> 
> On Thursday 15 September 2005 03:56 am, Tristan Tarrant wrote:
> > On Thu, 2005-09-15 at 10:42 +0200, Andreas Haumer wrote:
> > > That being said, I'd like to bring up again a subject I have 
> > > already mentioned on the list several times, but without any reply 
> > > so far: Caching at the DB access layer! As I tried to explain I 
> > > think that it might help to improve the performance of OpenCMS 
> > > quite noticable and reduce the load on the RDBMS at the same time. 
> > > DB access cache is an important and widely used technique for DB 
> > > applications in general and especially for web applications. If 
> > > done right, the advantages usually are considerable!
> >
> > Here is how I would work on opencms' db layer:
> >
> > - Implement a Hibernate CmsDbDriver. This would bring many 
> > enhancements to OpenCMS: more database portability, usage of 
> > container-provided datasource, automatic caching (Hibernate can use 
> > many libraries for
> > caching: ehcache, oscache, etc), no need to maintain several drivers 
> > for each database provider
> > - At the setup level implement a hibernate page which automatically 
> > scans the jndi tree for available DataSources, probing the 
> > underlying database type (the db dialect in hibernate-speak).
> >
> > Obviously I need a few rainy days to work on this :)
> >
> > Tristan
> >
> >
> >
> >
> > _______________________________________________
> > This mail is send to you from the opencms-dev mailing list To change 
> > your list options, or to unsubscribe from the list, please visit 
> > http://mail.opencms.org/mailman/listinfo/opencms-dev
> >
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list To change 
> your list options, or to unsubscribe from the list, please visit 
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>


_______________________________________________
This mail is send to you from the opencms-dev mailing list To change your
list options, or to unsubscribe from the list, please visit
http://mail.opencms.org/mailman/listinfo/opencms-dev