> More freedom, more control, more complex. Quite hard to avoid that.
Agreed. The challange is to define what parts need to be customized
often, and should be easy to change. For me, these bubbles should be
easy to change.. but as always, others may have a different oppinion.
> I cannot speak for the project, but I think Tapestry tries to be a Web
> framework, not a full stack. At least not yet. ;)
For me, authentication is an important part of a web framework and
should provide some standard way to do so.
> I was talking about a really generic tapestry-tx that could be used with any
> persistence technology, being it backed by relational database or not.
Great! Really looking forward to this.
> IMHO, using JPA or JDO over a non-relational database loses some of the
> benefits of it. I plan to write some projects to run on Google Application
> Engine and I'm going to use the low-level API.
Agreed. The native APIs are much easier in many cases. JPA as a whole
does not even fit well with non relational databases. JDO on the other
hand does - it was designed from the ground up to support different
types of persistence engines.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
