Greetings,
I am a new lurker over the past few days. I haven't been through all of
the mailing list archives yet. We built a lot of our website with the
ArsDigita Community System version 3.4. We were pleased with it, as it
enabled us in many cases to focus on the problem at hand and not on the
tool (much).
Now we are faced with building some more complicated database-driven web
applications and might need to add staff. TCL programmers are a little
hard to come by, and ACS Java as it stands I don't think is ready for
prime time. ACS 5 will go beta in a few weeks, but there is lots of
question about the future of ArsDigita since the departure of Philip
Greenspun. OpenACS is possibly a viable alternative, but that would
keep us in the TCL world and I don't know if I want to stay there.
I really like the idea of the MVC paradigm--that kind of thing is
totally absent from the 3.x series of the ACS. I was wondering if any
of the list members had experience with Enhydra, ACS (Java or TCL), and
(obviously) Turbine, possibly in conjunction with Cocoon. Can anyone
comment (objectively :-) ) on why they would pick one over another?
And regarding Turbine directly, something that concerns me greatly is
the way a Turbine app has to interface with the database--via the Peer
objects, right? The ACS has a great database API that makes handling
selects easy, but most of your SQL statements end up in the page code
itself. I'd really like to leave most of the business logic in the
database, is it easy to do that with Turbine? Is working with the Peer
objects a real pain? What if I need to slap a quick page on our site
that pulls a query from the database and shows it in a table. In
Turbine, is that easy, or not?
Sorry about the ramble--I'm having a hard time getting my head around
this development model...Thanks in advance for any help.
--cro
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
