Re: [Zope-dev] _p_deactivate() and _v_ variables?

Casey Duncan wrote: I would argue that a better plan would be to only use _v_ vars for completely disposable data only. The application should expect that this values will be gone at any random time, not just at transaction boundaries. Agreed. Are there any situations, apart from the already disc

Re: [Zope-dev] _p_deactivate() and _v_ variables?

Dieter Maurer wrote: Chris Withers wrote at 2003-10-8 21:22 +0100: > Casey Duncan wrote: > > > I would argue that a better plan would be to only use _v_ vars for completely > > disposable data only. The application should expect that this values will be > > gone at any random time, not just

Re: [Zope-dev] Very fast requests beating ZODB commits...

Tres Seaver wrote: Its funny nonetheless that you should report such a thing: we have a customer who reports similar issues in a bit of their CMS, where a popup submits its form (in Javascript) and then refreshes its parent window; if the commit takes long enough (e.g., it hits a conflict), the pa

Re: [Zope-CMF] Re: [Zope-dev] _p_deactivate() and _v_ variables?

Toby Dickenson wrote: Today we have the 'transaction participant' interface. That would be a better place to hold these things, allowing the DA object itself to be deactivated if necessary. What's the 'transaction participant interface' and where can I find otu mroe about it? Chris __

Re: [Zope-dev] _p_deactivate() and _v_ variables?

On Wednesday 15 October 2003 12:47, Chris Withers wrote: > Casey Duncan wrote: > > I would argue that a better plan would be to only use _v_ vars for > > completely disposable data only. The application should expect that this > > values will be gone at any random time, not just at transaction > >

Re: [Zope-dev] _p_deactivate() and _v_ variables?

Chris Withers wrote: Casey Duncan wrote: I would argue that a better plan would be to only use _v_ vars for completely disposable data only. The application should expect that this values will be gone at any random time, not just at transaction boundaries. Agreed. Are there any situations, apart

[Zope-dev] manage_workspace changes

Hi! As also mentioned here some CMF tool tabs are broken if used with a current Zope-2_6-branch checkout. I didn't spend much time to find out what's really going on here, so I might be missing something. But it looks like

Re: [Zope-dev] _p_deactivate() and _v_ variables?

Seb Bacon wrote: Agreed. Are there any situations, apart from the already discussed CMF skindata, where this currently isn't the case? I'm a bit puzzled - of what use is a variable which may disappear "at any random time"? For caching things... Chris __

Re: [Zope-dev] _p_deactivate() and _v_ variables?

Seb Bacon wrote: Chris Withers wrote: Casey Duncan wrote: I would argue that a better plan would be to only use _v_ vars for completely disposable data only. The application should expect that this values will be gone at any random time, not just at transaction boundaries. Agreed. Are there

Re: [Zope-dev] _p_deactivate() and _v_ variables?

On Wednesday 15 October 2003 14:53, Casey Duncan wrote: > >> Agreed. Are there any situations, apart from the already discussed > >> CMF skindata, where this currently isn't the case? > > > > I'm a bit puzzled - of what use is a variable which may disappear "at > > any random time"? > > It's not e

[Zope-dev] WebDAV and UTF-8 filenames

Hi guys! I've been hacking around a bit with Zope to try to support some non-ascii characters in the id's. Yes, I know it looks ugly in the URL's but when you go via WebDAV, that is not an issue. :) Anyhow, getting your Zope-object to accept non-ascii characters is not that hard, of course. Bu

Re: [Zope-dev] _p_deactivate() and _v_ variables?

Toby Dickenson wrote: On Wednesday 15 October 2003 14:53, Casey Duncan wrote: Agreed. Are there any situations, apart from the already discussed CMF skindata, where this currently isn't the case? I'm a bit puzzled - of what use is a variable which may disappear "at any random time"?

Re: [Zope-dev] WebDAV and UTF-8 filenames

If you set the "management_page_charset" property to "utf-8" in a folder (even the root folder) then Zope will inform the browser that the charset of the management pages of this folder and all subobjects is utf-8 and the IDs in the folder listing page will look right. Cheers, Leo -- Ideas don't

Re: [Zope-dev] _p_deactivate() and _v_ variables?

On Wednesday 15 October 2003 15:51, Casey Duncan wrote: > As it is, the hard cache > implementation, although beneficial from a memory management perspective > cause loaded servers to do alot more work because they are constantly > pruning the cache and then reloading objects again immediately the

Re: [Zope-dev] WebDAV and UTF-8 filenames

Leonardo Rochael Almeida wrote: If you set the "management_page_charset" property to "utf-8" in a folder (even the root folder) then Zope will inform the browser that the charset of the management pages of this folder and all subobjects is utf-8 and the IDs in the folder listing page will look righ

Re: [Zope-dev] WebDAV and UTF-8 filenames

On Wed, 2003-10-15 at 12:50, Lennart Regebro wrote: > Leonardo Rochael Almeida wrote: > > If you set the "management_page_charset" property to "utf-8" in a folder > > (even the root folder) then Zope will inform the browser that the > > charset of the management pages of this folder and all subobje