Have you folks looked into JSR-170, the Java Content Repository spec?
It covers these classes of use cases pretty thoroughly and there are
some very compelling implementations out there. Alfresco is probably
the most notable and Apache JackRabbit is pretty impressive as well.
Mike
(new to the list, please forgive me if I've violated some protocol
known to long-term list members...)
On Jul 1, 2009, at 8:12 PM, Adrian Crum wrote:
>
> --- On Wed, 7/1/09, David E Jones <dejc@me.com> wrote:
>
>> From: David E Jones <dejc@me.com>
>> Subject: Re: webslinger quick start guide?
>> To: dev@ofbiz.apache.org
>> Date: Wednesday, July 1, 2009, 2:45 PM
>>
>> This is an interesting overview and while I'm not sure why
>> I hadn't thought along these lines before, at least it's
>> through my thick skull now...
>>
>> I asked Adam about how this would deploy on multiple
>> servers with the stuff in the filesystem versus the
>> database, and I think what you've written Ean is the
>> answer.
>>
>> Why not treat a source repo (either plain SVN or something
>> more exotic like GIT) like the database? Each app server
>> would read from and write to the source repo just like it
>> would a database record. If SVN or GIT support 2-phase
>> commits we could probably even do write operations in the a
>> transaction that includes connections to both data stores.
>
> Why not have the repositories use the OFBiz database as their data
> store?
>
> -Adrian
>
>
>
>
|