All the IBM development sounds sweet to me... I would love to get as
much of it integrated into Roller as possible.

I'm afraid I'm one of those developers 'toiling' away at Roller and
haven't really introduced myself to the Roller community and thought
that this was a good opportunity.  For the last 6 months I've been
turning Roller into photoblogging platform - you can see the most
up-to-date version @ www.pixyblog.com.  Unlike the IBM developments,
the majority of the current changes I've made to Roller would not be
beneficial for inclusion into the Roller webapp, but I expect this to
change as my project develops.

As for my 2 cents on the JPA vs iBate discussion - as long as it works
and is easy to work with I have no preference, but I agree with Elias
that I don't see the benefits for Roller to support multiple backends.

Great project guys!  I love working with the Roller source ;-)

Cheers,

Richard Jones



On 30/01/07, James M Snell <[EMAIL PROTECTED]> wrote:
simplest + most efficient + easiest to optimize.

- James

Elias Torres wrote:
>[snip]
> multiple-implementations story doesn't convince me. All we need is one
> that works with the different dbs and it's easy to use. The simpler
> the better.
>
> -Elias
>


Reply via email to