On Thursday 14 November 2002 04:36 am, Steve Alexander wrote:
Casey Duncan wrote:
It is only there due to lack of time to take it out. We had planned to
take it
out for 2.6, but time was never made to replace it with code to
bootstrap an
empty storage with the proper root level
Whilst we are on the subject, I now ship the Plone Windows Installation (and
I think the Mac) without a ZODB, it monkey patches
OFS.Application.initialize to add in the Plone stuff on start up. This lets
us do some neat stuff and make a smaller download.
Im not sure how zope 3 does it, but I was
Working on updating my ZOPE and ZEO RPMs I got
to wondering...
What's in the default data.fs that ships with
Zope? I mean, ZEO (actually ZODB) auto-creates
a data.fs when one isn't found, so why does
Zope come with one?
Or if there -is- something Zope-specific in
data.fs, then shouldn't there
It is only there due to lack of time to take it out. We had planned to take it
out for 2.6, but time was never made to replace it with code to bootstrap an
empty storage with the proper root level elements still residing in
Data.fs.in.
-Casey
On Wednesday 13 November 2002 02:22 pm, Jeff Rush
I don't quite understand -- so there *are* root
level elements specific to Zope that need to
be copied into a Zope-over-ZEO environment?
(hm, how do those elements get into a
non-FileStorage Zope-over-ZEO environment?)
And do those elements interfere even a little in
a non-Zope-just-ZEO
