Re: AW: AW: [Objectbridge-jdo-dev] Introduction

[Andy L. <aj...@as...>]

Ok...so is this, as it appears to be, a cross-community consensus that:

- Sparrow will focus on JDO with a pluggable architecture
- ORB will focus on a clean, core O/R engine

Implying further that:

- Both communities have a vested interest in getting the Sparrow JDO front
end working on the ORB kernel
- Each project will effectively "endorse" the other
- People will be encouraged to contribute to both efforts when possible
- Sparrow become the JDO interface to ORB
- ORB becomes the "default" plug-in back end for Sparrow

Tell me if I have asserted facts not in evidence here....


> Hi Joel, Hi Andy,
>
>> I would like to second your suggestion that Sparrow do #1
>> because... #3
>> might not be part of the Sparrow project after all. For example, I
>> mentioned Ozone. Sparrow could be the front JDO with pluggable stores
>> architecture, and Ozone or other object databases could then do their
>> own work to conform to that pluggable architecture.
>>
> excluding #3 from the Sparrow scope will be the best solution to get
> Sparrow started as fast as possible.
>
>> Thus... let's call Sparrow the front end JDO architecture and if I
>> decide to do a new optimized object storage for it (which I
>> would really
>> like to but don't know if I'll have time), that could be the third
>> project.
>>
>> How does that sound?
>
> For me it's definitely OK!
>
> So when will you have finished #1? ;-)
>
> cu,
>
> Thomas
>
>> --
>> Joel Shellman
>> Comprehensive Internet Solutions -- Building business dreams.
>> [ web design | database | e-commerce | hosting | marketing ]
>> iKestrel, Inc.  http://www.ikestrel.com/
>>


"The heights of genius are only measurable by the depths of stupidity."