<br><br><div><span class="gmail_quote">On 9/2/05, <b class="gmail_sendername">Chris Withers</b> <<a href="mailto:chris@simplistix.co.uk">chris@simplistix.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Marco Bizzarri wrote:<br>><br>> Users should have their own storage, so that they can create/modify objects<br>> inside that, without influencing the general, shared database.<br><br>The ZODB mounting machinery isn't designed for this case and it would
<br>take a lot of work on your part to make it do what you need, although it<br>should certainly be possible.</blockquote><div><br>
Ok, I will not purse this for this moment.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What about not influencing the general, shared database (can you tell us<br>more about what that is?) means that you think you need seperate storages?
</blockquote><div><br>
I will try to better explain myself on what we are actually doing. <br>
<br>
The context is PAFlow, which is a "pure" (no CMF/Plone) vertical application for (italian) public administration.<br>
<br>
Inside this application, we are using an in house developed framework
where more or less each page shown to the user is connected to an
object (which we call controller) on the ZODB.<br>
<br>
When one user requests a page, PAFlow creates a controller for it
(actually, creates also the page, but this is not important now),
storing there all the data meaningful for that page, so that later the
page can be built simply by invoking methods from the controller (I
hope this is clear, otherwise I will post some code example).<br>
<br>
Of course, the creation/destruction of all these objects is a major performance problem, because they happen all on the ZODB.<br>
<br>
Since these are temporary data, we would like to create them in a
temporay storage, either one for each user or one for all of them.<br>
<br>
We could create them in the /temp_folder, but this could provide some
non trivial security issue (?), also because you can have more than one
PAFlow Site installed in a ZODB.<br>
<br>
What are the data stored on the ZODB, apart from the controllers?
Workflow data for ongoing processes. All the domain data are stored on
a RDBMS.<br>
<br>
I hope I explained myself.<br>
<br>
Thanx for your inputs :) <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">cheers,<br><br>Chris<br><br>PS: You shouldn't be using DBTab in this day and age, upgrade your Zope
<br>version and use zope.conf...</blockquote><div><br>
I did not explain myself: I'm not using dbtab, actually. I was
exploring the way in which I could achieve what I would like to do and,
exploring the code, I stumbled upon dbtab. We're working on 2.7.x, with
zope.conf<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--<br>Simplistix - Content Management, Zope & Python Consulting<br> -
<a href="http://www.simplistix.co.uk">http://www.simplistix.co.uk</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Icube Srl<br><a href="http://www.icube.it/">http://www.icube.it/</a><br>