Shane Hathaway wrote:
> An idea just occurred to me.  I think others have probably had similar
> ideas, but didn't express it in the right place or time.
> Part 1: Let's put an Apache-like web root (similar to
> /var/www/localhost/htdocs/) in Zope instance homes.  It might be called
> "browser" or "www".  Zope will serve pages out of that web root rather
> than an object database.
> Part 1 rationale: When people create a Zope instance home, they create
> some config files and an object database.  The root of the site is
> served out of the object database.  To change the default page, newbies
> are directed to create a default page in the object database.  The user
> didn't ask for an object database.  The use of an object database should
> be a choice, not a requirement.  Now the user has to learn some extra
> tools (fssync, etc.) in order to put the files under version control.  I
> think the user experience for both newbies and experts would be much
> better if the root of the site were served from a filesystem directory.

> Any thoughts or gut reactions?
> Shane

+1 from the standpoint of promoting corporate adoption, especially when
combined with first-class citizenship for RDBMS. (In the corporation I
work for, anyway.)

-- Wade Leftwich
Ithaca, NY
Zope3-dev mailing list

Reply via email to