Ivo van der Wijk writes:
> On Wed, Apr 17, 2002 at 07:54:04AM -0400, Paul Everitt wrote:
> > Let's take the next step and say that you can live with a little
> > volatility in the data. You write an object that caches ten seconds
> > worth of writes. Whenever a write comes in at the over-t
Max Slimmer writes:
> I have created a zclass and want to create a new instance of this class and
> have it be child of some other know object in the tree.
> Given that we know the path (url) to the new prospective parent how do we do
> this.
You locate the destination object with "restrictedT
> "Chris" == Chris Withers <[EMAIL PROTECTED]> writes:
> Well, is there any way I can easily tell emacs:
> - If a file starts with or html-mode
> - If a file starts with #, then go into python mode?
Asking "is it possibile in Emacs..." ?
You are joking!
I did my
Toby Dickenson <[EMAIL PROTECTED]> wrote:
> >This reminds me of a question I had: given that (from what I understand)
> >_v_ attributes only live in the object cache of a given Zope,
>
> True, and more accurate that I think you expected
>
> The issue is that one Zope has more than one ZODB
> Ive never looked at LDAPUserFolder so this may be irrelevant, but is
> it possible for LDAPUserFolder to validate that the cached _v_
> information is still fresh? If that validation is quicker than
> fetching a new copy then this is still an overall win.
yes it does have a very rough way of va
On Thu, 18 Apr 2002 16:23:15 + (UTC), Florent Guillaume
<[EMAIL PROTECTED]> wrote:
>This reminds me of a question I had: given that (from what I understand)
>_v_ attributes only live in the object cache of a given Zope,
True, and more accurate that I think you expected
The issue is that
Jeremy Hylton wrote:
>>"CM" == Chris McDonough <[EMAIL PROTECTED]> writes:
>
>
> >> Completely agreed. My disagreement is portraying the counter
> >> problem as impossible with the zodb. I think some people, as
> >> evidenced by some of the responses, are willing to live with the
Jeremy Hylton wrote:
>>"CM" == Chris McDonough <[EMAIL PROTECTED]> writes:
>
>
> >> Completely agreed. My disagreement is portraying the counter
> >> problem as impossible with the zodb. I think some people, as
> >> evidenced by some of the responses, are willing to live with the
Florent Guillaume wrote:
>
> Or am I misunderstanding something ? My question really relates to any
> use of _v_ as a cache that can survive on publisher transaction, really.
> Should _v_ never be used like that ?
There's a case to be made for attributes that not persisted (like _v_
attributes)
Toby Dickenson <[EMAIL PROTECTED]> wrote:
> > Whenever a write comes in at the over-ten-second mark,
> >you write the _v_ attribute to the persistent attribute.
>
> That would be bad. _v_ attributes are lost when the object is
> deactivated and removed from the ZODB memory cache It would l
> "CM" == Chris McDonough <[EMAIL PROTECTED]> writes:
>> Completely agreed. My disagreement is portraying the counter
>> problem as impossible with the zodb. I think some people, as
>> evidenced by some of the responses, are willing to live with the
>> tradeoffs. Other people will
Hello Brian.
* Brian Lloyd <[EMAIL PROTECTED]> [2002-04-17 20:29]:
> Ok. I'd like to run the mbox thing by Jim to see if he has any
The product now uses a Maildir-style approach to deal with
concurrent writes. The creation of the file name uses
time(), gethostname() and randint() to hopeful
12 matches
Mail list logo