Re: [Zope3-dev] Hyping Zope3 contest? (was: Selecting a code name)
Gary Poster wrote: [snip] You say this in your other message: Somehow people don't seem to be discussing other activities much in the recent threads, such as the writing intro text, of tutorials, designing and presenting screencasts, gathering links and other information. Seems like just the sort of individual things that a split-up competition would be good for, to me. Add in something silly, like most fun logo or silliest slogan, just for spice, and it even sounds like you have a nice balance of categories. I fear that a split up competition will have a lot of people come up with slogans, some with logos, and nobody with a decent tutorial. Your list also sounds like things that can be done out of the context of a grand website effort, and used as useful raw materials for such an effort. Again, I believe that without fixing Zope's web presence all other Zope marketing activities are pretty much futile. *Within the context* of the zope web presence this can work, of course, but I expect people to do a bit more work than just talk. I may be wrong about this; if so please give me the reasons I'm missing why a slogan or logo in isolation would really help Zope's marketing. Whatever, I was only volunteering to try and help. I'm beyond, beyond swamped. I'm thrilled that folks are working on the zope.org site. Thank you. I'm not doing much, but I took a few hours a few months ago to write some text, and since then I'm spending time trying to get other people to do some bits as well. Some people have been doing so. I think if we can just keep this up we can get somewhere. Perhaps other loose boutique sites, as I had envisioned, for individual projects such as the Zope 3 effort, can grow at a later time. Right now I expect we may end up doing the following: * create a boutique site for Zope. No community features, but nice presentation and intro text, and download information for Zope. * from this, create a resource for zope 3 in the form of tutorials, screencasts. This may be on another site or part of the original site. I think we'll get the most energy in producing Zope 3 compared to Zope 2, so we'll go with the flow. * retire zope.org as much as possible and replace it with the new frontend. Quite possible we cannot do this straight away at all - We need it for all the resources hidden away in it, and I worry about breaking links, so this is a problem. We also have a working zope extension upload system on there that I worry about replacing. Just replacing its outer layer with a boutique website of Zope may however be enough already. I'm happy to see a competition for a boutique site, and whether people present a new zope.org or zope3.org is up to them; this may influence whether we end up with a separate zope3.org or an integrated zope.org. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Hyping Zope3 contest? (was: Selecting a code name)
On 2/9/06, Martijn Faassen [EMAIL PROTECTED] wrote: I fear that a split up competition will have a lot of people come up with slogans, some with logos, and nobody with a decent tutorial. Well, that may be true. But on the other hand, if there are people working on a decent tutorial now, then they will probably have no competition anyway, and if nobody is working on a tutorial now, or during a tutorial competition, then we are in trouble anyway. Again, I believe that without fixing Zope's web presence all other Zope marketing activities are pretty much futile. Yup. I may be wrong about this; if so please give me the reasons I'm missing why a slogan or logo in isolation would really help Zope's marketing. It wouldn't. I guess the idea is to get more people involved in helping Zope3s marketing. A competition may not be the answer. But then again, it might. :) The alternative is to design by comittee, which is what gave us the current zope.org. That took a very long time, and it seems nobody is happy with the results... * create a boutique site for Zope. No community features, but nice presentation and intro text, and download information for Zope. Yes, this is what we should concentrate on. And maybe we don't need to compete about everything, but how about making a competition for a flash-demo? Yes, I want a flash-demo. No, I don't know how to make one. I'm happy to see a competition for a boutique site, and whether people present a new zope.org or zope3.org is up to them; this may influence whether we end up with a separate zope3.org or an integrated zope.org. I think we should definitely go for zope3.org, both to separate Zope2 and Zope3 and because zope.org currently is such a vast mess that replacing it is pretty much out of the question. If we start to think about replacing it in the future, the way to go in my opinion is to make many separate microsites with separate aims, and only one thing in common: logins. collectors.zope.org products.zope.org devwiki.zope.org news.zope.org whatever.zope.org somethingelse.zope.org This way upgrades in the future can become easier as we can do one site at a time, instead of necessarily doing all of Zope.org at one time. But first, lets concentrate on the boutique for Zope3. That's what's most desperately needed. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] rdb: Disappearing Connection redux
Hi Jim, Jim Washington wrote: The situation I wish to handle is the case where MySQL server silently closes its connection with Zope after 8 hours idle, which likely will happen at least once a day. What seems to work for me now is the following as mysqldbda.adapter.MySQLdbAdapter.isConnected() def isConnected(self): try: self._v_connection.ping() except: # not connected or ping did not restore MySQL connection if self._v_connection is not None: self._v_connection.close() self._v_connection = None return False return True After experiencing 'Mysql server had gone away' errors I quickly found this thread. If I interpret the course of discussion correctly, the above isConnected implementation solved this problem for you, right? I add this implementation of isConnected to the mysqldbda in my setup (Zope-2.9 + Five + sqlos, mysql 4.1.12) too, and things *seem* to have improved. But not completely, every now and then I get the gone away errors again. Question is, was this indeed the final conclusion for this thread and did it solve the problem for you completely - i.e. do you not get the gone away errors anymore? kind regards, jw -- Jan-Wijbrand Kolman [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] 'Adding' view for container
On Wednesday 08 February 2006 15:57, Garanin Michael wrote: In 3.2 version 'Adding'-view for container was 'zope.app.container.browser.adding.ContentAdding' class but in new trunk version it's 'Adding' class. 'ContentAdding'-deprecated (such as 'add_content'-menu) and must be removed or it's bug? Hi Garanin, I am sorry, but I am not sure what you are saying asking. It is right that the ContentAdding is deprecated. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] WebDAV
On Wednesday 08 February 2006 16:18, Michael Kerrin wrote: WebDAV Interfaces, Widgets and Adapters http://www.zope.org/Members/mkerrin/WebDAVInterfacesWidgetsAndAdapters This defines changes that I see has crucial but which introduce nasty backwards compatibility problems. So it would be handy to know who has developed any custom extension to zope.app.dav be it a custom adapter to zope.app.dav.interfaces.IDAVSchema or who have developed a custom WebDAV namespace (these are the two likely areas for problems). I am hoping that this figure is small :-) Hi Michael, It is good to finally see a real technical discussion again. I hope Jim is reading the list again. :-) I really like this proposal, since it fixes the WebDAV support to a state where it should be. I honestly doubt that anyone has been using WebDAV until now. Thus I would not worry about BBB at this point, but it is still good that you are asking! Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] WebDAV
On Wednesday 08 February 2006 16:18, Michael Kerrin wrote: WebDAV? Namespace Management http://www.zope.org/Members/mkerrin/WebDAVProposal/wikipage_view Here I define how, and why, I am planning to manage a WebDAV namespace. This includes how to find which properties are defined on a object, and what widget to use to display the property, and how to extend an already registered WebDAV namespace. My goal for all this has being to develop zope.app.dav to a point where it can handle all of the WebDAV protocol details according to the RFC2518 specification, while only requiring a minimal knowledge of WebDAV from developers who just wish to integrate WebDAV protocol into there application. Michael, this is also an excellent proposal. I really like it! I think with this and the other proposal, the Zope 3 WebDAV story will look really good. The only outstanding problem is with the arbitrary namespace data that we might receive. Have you thought about that already? I don't want to add more work, so if you do not want to think about this, then just ignore the question. :-) Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Automated compatibility tests
On Wednesday 08 February 2006 07:53, Max M wrote: Does anybody have an idea as to what is necessary to do these automated tests, or links to previous efforts in this direction? I imagine something like the testrunner that is currently testing out Zope. Or am I the only one seing this as a problem that should be automated? I am in the process of writing a proposal that should address this issue for a set of fundamental packages. I really hope that eggs will solve this issue for us eventually. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] zope.schema: defaults for non-immutables... questions
On Tuesday 07 February 2006 13:11, Shaun Cutts wrote: By delegation support I mean support for being a proxy for an interface, and delegating its fulfillment to a subobject. Okay, the explanation helped a lot, though I do not like it. But people on the zope.interface list might feel different. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] WebDAV
On Thu, Feb 09, 2006 at 06:20:46AM -0500, Stephan Richter wrote: | Michael, | | this is also an excellent proposal. I really like it! I think with this and | the other proposal, the Zope 3 WebDAV story will look really good. By all means! From the POV of having implemented the current webdav namespace support, I really enjoy the proposals. They make use of some features that were not present/too obscure when the initial implementation was done and solve the major glitches that I've found. +1. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] WebDAV
Hi Stephan, On Thursday 09 February 2006 11:20, Stephan Richter wrote: On Wednesday 08 February 2006 16:18, Michael Kerrin wrote: WebDAV? Namespace Management http://www.zope.org/Members/mkerrin/WebDAVProposal/wikipage_view [snip] this is also an excellent proposal. I really like it! I think with this and the other proposal, the Zope 3 WebDAV story will look really good. The only outstanding problem is with the arbitrary namespace data that we might receive. Have you thought about that already? I don't want to add more work, so if you do not want to think about this, then just ignore the question. :-) I haven't really thought about it until now but it should fit into the proposal, but I am hoping it goes something like this. I think I need to play with some test implementation just to make sure. PROPFIND and PROPPATCH will know if a property is dead or not, considering that they are responsible for finding the correct namespace utility, so they could ask for standard dead namespace management utility. This utility can then generate on the fly a dead WebDAV widget and probable a dead property field and then everything continues has normal. I hope :-) To be honest I was a bit caught up in all the WebDAV namespace / specs that I forgot about dead properties until sometime early this week. But I am confident that I can get something alone these lines working without to much trouble. Michael -- Michael Kerrin 55 Fitzwilliam Sq., Dublin 2. Tel: 087 688 3894 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] WebDAV
On Thursday 09 February 2006 11:06, Stephan Richter wrote: On Wednesday 08 February 2006 16:18, Michael Kerrin wrote: WebDAV Interfaces, Widgets and Adapters http://www.zope.org/Members/mkerrin/WebDAVInterfacesWidgetsAndAdapters This defines changes that I see has crucial but which introduce nasty backwards compatibility problems. So it would be handy to know who has developed any custom extension to zope.app.dav be it a custom adapter to zope.app.dav.interfaces.IDAVSchema or who have developed a custom WebDAV namespace (these are the two likely areas for problems). I am hoping that this figure is small :-) Hi Michael, It is good to finally see a real technical discussion again. I hope Jim is reading the list again. :-) :-) I really like this proposal, since it fixes the WebDAV support to a state where it should be. I honestly doubt that anyone has been using WebDAV until now. Thus I would not worry about BBB at this point, but it is still good that you are asking! Great - this is what I have being hoping for :-) Thanks Michael -- Michael Kerrin 55 Fitzwilliam Sq., Dublin 2. Tel: 087 688 3894 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] rdb: Disappearing Connection redux
On Thu, Feb 09, 2006 at 11:54:18AM +0100, Jan-Wijbrand Kolman wrote: I add this implementation of isConnected to the mysqldbda in my setup (Zope-2.9 + Five + sqlos, mysql 4.1.12) too, and things *seem* to have improved. But not completely, every now and then I get the gone away errors again. Make sure you have a sqlos revision after 22260, as before that sqlos was caching connections (even ones where the server has gone away). -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Zope 3 web root
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. Part 2: Let's add some ZCML directives that define how to interpret filenames in the web root by their extension. Let's also interpret special per-directory files that map URI names to filenames, similar to Apache .htaccess files. Part 3: One kind of file we can put in the web root serves as a gateway into an object database. We might use the extension .zodb for this purpose. The .zodb file would specify what kind of storage to open, where to find it, and what object to load from it. In a sense, the web root would mount the object database. Some configuration of the web root would mount an object database right at the root, enabling Zope 3 to act just like it does today. Any thoughts or gut reactions? Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
RE: [Zope3-dev] Zope 3 web root
Hi Shane -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shane Hathaway Sent: Thursday, February 09, 2006 7:41 PM To: zope3-dev@zope.org Subject: [Zope3-dev] Zope 3 web root 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. Part 2: Let's add some ZCML directives that define how to interpret filenames in the web root by their extension. Let's also interpret special per-directory files that map URI names to filenames, similar to Apache .htaccess files. Part 3: One kind of file we can put in the web root serves as a gateway into an object database. We might use the extension .zodb for this purpose. The .zodb file would specify what kind of storage to open, where to find it, and what object to load from it. In a sense, the web root would mount the object database. Some configuration of the web root would mount an object database right at the root, enabling Zope 3 to act just like it does today. Any thoughts or gut reactions? That's a very interesting idea. Do you mean something like this: instance | -- var/poll.fs | -- wwwroot | -- index.html (file system) | -- pollApplication.zodb (zope) | (file with info that point/maps to ../../var/poll.fs) | -- staticFolder (file system) | -- index.html (file system) This means the pollApplication contains a index.html view/page and poll application driven by Zope. Where the rest of the structure is served by static folders and HTML files. Did I got it right? This could be very useful for smaller websites which only need some small dynamic pages and do not need all the overhead from zope. I think about some poll apps or just a view with some database information etc. Regards Roger Ineichen Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
Roger Ineichen wrote: That's a very interesting idea. Do you mean something like this: instance | -- var/poll.fs | -- wwwroot | -- index.html (file system) | -- pollApplication.zodb (zope) | (file with info that point/maps to ../../var/poll.fs) | -- staticFolder (file system) | -- index.html (file system) Yes. This means the pollApplication contains a index.html view/page and poll application driven by Zope. Where the rest of the structure is served by static folders and HTML files. Did I got it right? Essentially right, but the content is not necessarily static. The ZCML might choose to map the extension .zpt to page templates and the extension .py to Python scripts. This could be very useful for smaller websites which only need some small dynamic pages and do not need all the overhead from zope. I think about some poll apps or just a view with some database information etc. It's also useful for big sites that use a relational database rather than an object database, or only need an object database for certain parts. The feature would make Zope easier to use for new projects, prototypes, and one-off web sites. There is some irony in that statement. Back in 1999 or so, a lot of web designers had trouble uploading files to a web server, and Zope's TTW editing was a nice solution, so lots of people came to Zope just for that. Today, nearly every cheap web hosting plan includes TTW editing and a host of other dynamic features, so the need for editing HTML and scripts TTW has almost dried up. Zope's market now consists of people who have command line access and know how to use subversion, rsync, and NFS / CIFS. Today, editing on the filesystem is a more productive and enjoyable experience. Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
On Feb 9, 2006, at 9:25 PM, Shane Hathaway wrote: Roger Ineichen wrote: That's a very interesting idea. It is a very neat idea. You asked for gut reactions, and I must admit that I regard the ZODB as more attractive and more central to the Zope story than some, so my gut reaction is lukewarm. I can imagine sites like the ones you described, though, and have even made one or two that might have used this...though not at work. Come to think of it, maybe it would also be an interesting approach to a baked web site delivery system. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
I agree that this is an interesting idea. I have a couple thoughts. * There's something appealing about a collection of files that describe how URLs are mapped to databases, static files, etc. This could serve as a sort of site map for developers. * I agree with Roger this might make sense for small projects. However, for the small projects that I work on I more often need dynamic but not persistent stuff, rather than static file serving. So this proposal would appeal more to me if one could mount non-persistent object, e.g. modules in the URL space (a la Bobo). -Amos ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
Gary Poster wrote: On Feb 9, 2006, at 9:25 PM, Shane Hathaway wrote: Roger Ineichen wrote: That's a very interesting idea. It is a very neat idea. You asked for gut reactions, and I must admit that I regard the ZODB as more attractive and more central to the Zope story than some, so my gut reaction is lukewarm. I agree that ZODB is very central, but I think there are a lot of people who would use Zope if they didn't have to simultaneously commit to ZODB right away. I can imagine sites like the ones you described, though, and have even made one or two that might have used this...though not at work. The big thing for me is the migration story. First, I (as a web designer, novice or experienced) build a web site for my company or I conceive of some fun new idea like del.icio.us. I make a little site in the web root, using Zope technology, with only one dead but familiar chicken: filename extensions. If the site I build turns out to be reusable, I graduate into application development, and the transition is smooth since I'm already using Zope technology. I praise the developers of Zope for the nice learning curve. :-) Come to think of it, maybe it would also be an interesting approach to a baked web site delivery system. Maybe. I've come to think of baking as a pretty hard problem, though. It's like caching (which is often a hard problem) without invalidation. Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
Amos Latteier wrote: * I agree with Roger this might make sense for small projects. However, for the small projects that I work on I more often need dynamic but not persistent stuff, rather than static file serving. So this proposal would appeal more to me if one could mount non-persistent object, e.g. modules in the URL space (a la Bobo). Yes, you could, if there's a ZCML directive that says to do so. For example: map extension=.bobo handler=zope.webroot.handlers.Bobo / Then just create a .bobo file, with a format recognized by the Bobo handler. Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
FWIW, I'd be keen on seeing a bobolike Zope 3 derivation that included none or very little of zope.app, but that allowed you to configure an instance to publish a single arbitrary root object but assumed nothing else. I think the filesystem traverser root object could be one kind of root object. CherryPy is a bit like this now. - C On Feb 9, 2006, at 1:40 PM, 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. Part 2: Let's add some ZCML directives that define how to interpret filenames in the web root by their extension. Let's also interpret special per-directory files that map URI names to filenames, similar to Apache .htaccess files. Part 3: One kind of file we can put in the web root serves as a gateway into an object database. We might use the extension .zodb for this purpose. The .zodb file would specify what kind of storage to open, where to find it, and what object to load from it. In a sense, the web root would mount the object database. Some configuration of the web root would mount an object database right at the root, enabling Zope 3 to act just like it does today. Any thoughts or gut reactions? Shane ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/chrism% 40plope.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope 3 web root
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. A big -1 from me. This is yet more complexity and more stuff that Zope shouldn't try to do. If you want to serve flat files, use Apache. 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. But it's one of Zope's main strengths and I'd find it odd if newbies were directed to do anything other than use it ;-) The use of an object database should be a choice, not a requirement. I'd flip that, because I think you and Steve A would agree on one thing: The use of an object database _should_ be a choice, not a requirement, but it should also be the default ;-) So, to sum up, I reckon Zope should use ZODB by default, but it should be possible, without too much pain, to get it to use _just_ an ORM if you so desire. Flat files is Apache land, lets not try and compete there ;-) cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
