A coworker of mine wrote his own web server framework from scratch for an
internal application. We're looking to migrate this application to Zope
(thank God!). The only question we need to deal with is:
The reason he wrote his own webserver rather than use CGIs is that there
was some
On Fri, Apr 08, 2005 at 12:00:45PM +0200, Lennart Regebro wrote:
Is this persistent even among server restarts, or persistent per
request, or persistent per session? (the answer is different for all
of them, and usually, in Zope, persistent means persistent over
server restarts).
Ah, sorry.
On Fri, Apr 08, 2005 at 11:30:23AM +0200, bruno modulix wrote:
Look into Product, ZODB, and acquisition !-)
Excellent. It looks like persistence may not be an issue here, actually,
since I think the persistence I want -- hang around for the life of the
Zope server -- is built in anyway, right?
On Fri, Apr 08, 2005 at 06:48:49PM +0200, Lennart Regebro wrote:
But for the life of the server is rather unusual... What are the
objects you are doing, more specifically?
We're porting a web application to manage a collection of DNS and DHCP
servers. At startup time, we talk to each of these
On Fri, Apr 08, 2005 at 07:13:11PM +0200, Lennart Regebro wrote:
In that case I would just store the information as usual in the ZODB,
that is, the data is persistent across server restarts, but call a
method that updates it when you log in (or simply have a button to do
it).
That works.
