On Wed, 2007-07-11 at 10:38 +1000, Michael Ralston wrote:
> On 7/10/07, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> > On Tue, 2007-07-10 at 07:51 +1000, Michael Ralston wrote:
> > >
> > > To be honest, I'm sick of lenya. Because I recommended it to my
> > > employer and subsequently developed with it, I lost my job.
> > >
> >
> > The problem in your case I see is that you tried to change/rewrite lenya
> > completely regarding the backend. When I first read on the ml I thought
> > by myself it is overkill for one person and reading your mail now I
> > guess it really was.
> >
> > I do not think that the choice for Lenya is singly responsible for the
> > outcome of your recommendation/development. I guess that would have
> > happened with any other open source cms where you tried that radical
> > changes on your own.
> >
> 
> The core code which ran my backend was only 2-3 weeks of one person's
> work. That part of the code worked fine. It all fell apart when I
> tried to make lenya do more dynamic things like an amazon style
> shopping system with categorized products, searching, and ecommerce
> integration.
> 
> I don't think that sort of thing would ever be possible in lenya's
> current incarnation. Cocoon especially prevents lenya from being able
> to render pages dynamically. Eg, the shopping cart page which shows
> the products someone has selected to purchase. From memory, I  got the
> render time for a cart with 10-20 products down to about 0.2 seconds
> of server processing. That's simply unacceptable if you're going to
> have even 100 people hitting your site.
> 
> So in essence you're right. It was overkill. I was trying to make
> lenya do something it wasn't designed for.

Sad but true about the design limitations.

salu2
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to