Michael Wechner wrote:
Gregor J. Rothfuss wrote:
Michael Wechner wrote:
not using flow is of course not an option.
says who? I think it's of great importance that the community is
aware of the situation and has the capability of discussing things
before going ahead and
jumping over the cliff, which might sound a bit dramatic ;-)
once you take the time to understand the 1.4 code base, you'll see
why. the (rare)
it's not going to be rare, but rather essential in the near future
+1
Looking at http://lenya.apache.org/roadmap.html, industrial strength
is one of our "core competences". Even if technical people agree that
failover on an authoring server is not essential, management people
will generally not. And if we want to use flow for live applications,
it's quite essential anyway.
case of clustering does *not* mean we can inflict pain on everyone else.
I agree re the pain, and it might was a bit provocative, but we all need to
be aware of these issues
if someone needs clustering then they should be prepared to do the
necessary changes.
it's important that we get started somewhere and not introduce more stuff
which doesn't comply to clustering
Yes, we have to be careful. But rather than looking for alternative
solutions, I'd invest in solving the issue in Cocoon. From my perception
the pressure on the Cocoon community re. this problem is increasing.
Just my $0.02, but I'd love to see Lenya ready for clustering.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
