On Sat, 2006-01-21 at 01:43 +, Martin Aspeli wrote:
Hi,
I think this is very a unfortunate, and unfortunately also completely
understandable mistake. The Zope community has some great architects and
developers, but from looking at the state of zope.org, not many who are
willing or
This is unfortunate. I do think Zope 3 will get the recognition it deserves
in time. I feel the Zope community is more focused on how it works than how
it is marketed and this seems like the best long term approach.
People will shy away from it as it is not well known (like Linux in the
early
Zope stlll means Zope 2 even on the Zope website in many places.
I've encountered this same confusion in various places, and don't know
how long it will take for the word to get out or how long bloggers
and reviewers will have to take pains to explain the difference between
Zope 3 and Zope 2.
On Sat, 21 Jan 2006 14:11:12 -, David Johnson
[EMAIL PROTECTED] wrote:
This is unfortunate. I do think Zope 3 will get the recognition it
deserves
in time. I feel the Zope community is more focused on how it works than
how
it is marketed and this seems like the best long term
David Johnson wrote:
This is unfortunate. I do think Zope 3 will get the recognition it deserves
in time. I feel the Zope community is more focused on how it works than how
it is marketed and this seems like the best long term approach.
Actually I think Zope3 is in danger of being rendered
David Johnson wrote:
In general we’re looking at using an RDBMS, but we’re trying to
get a better feeling of when we can use the ZODB and when we
should stick to the RDBMS.
We have various datasets:
1. Transactions: 10-100 billion objects
2. Users: 10-100 million objects
3.
David Johnson wrote:
Thanks for the help. I think I understand, however, I think I might be
missing something. You specified that you would get a URL such as:
http://www.taupro.com/venture/IBM/ledger/100
This looks good, but it seems that the object is not persistent, and a
restart of
