Hi!
I would like to resurrect this thread with my own recent experience.
My problem was to spread a set of zodb objects over several zope
installations. Every installation required some slight modifications to
be applied to original objects (such as usernames and passwords).
So I decided to expor
It has not worked for a long time, and that's because not many people
use it. But those who do usually uses it a lot, so it would be bad if
it goes away.
I would propose that somone that uses this heavily (like the Nexedi
people), joins the Zope Foundation as a commiter, gets commiter rights
and
On 10/27/06, Lennart Regebro <[EMAIL PROTECTED]> wrote:
It has not worked for a long time, and that's because not many peopleuse it. But those who do usually uses it a lot, so it would be bad ifit goes away.I would propose that somone that uses this heavily (like the Nexedi
people), joins the Zope
On Friday 27 October 2006 16:46, Lennart Regebro wrote:
> I would propose that somone that uses this heavily (like the Nexedi
> people), joins the Zope Foundation as a commiter, gets commiter rights
> and holds his or her hands over this functionality. :)
We are definitely willing to help the main
On 10/28/06, Yoshinori Okuji <[EMAIL PROTECTED]> wrote:
for now, so I don't think I can do that. If it is acceptable to simply fix
the current code, we can provide patches.
Of course it's acceptable. Although it would as previously mentioned
be better if you could check them in yourselves inste
On 10/29/06, Yoshinori Okuji <[EMAIL PROTECTED]> wrote:
IIRC, Jim noted that it would be better to
backport zope3's, while our patches are for zope2's.
See http://mail.zope.org/pipermail/zope-dev/2006-May/027503.html for a
short thread on successfully using xmlpickle. With that recipe and
patch