improvement would be one way to improve this. I
think this would make a good fishbowl proposal
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
gratefully accepted.
http://collector.zope.org/Zope/737
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
On Friday 20 December 2002 2:22 pm, Kazuya FUKAMACHI wrote:
if all of them are included in Zope 2.6.1.
The final beta is due today. If that goes to plan then it is already too late.
2.6.2 is a realistic target.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
on my zope.
Good work. This definitely looks viable for 2.6.2
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
as { }, and it
will be as good as any other.
If you want an authentic ZPublisher namespace then you need
http://www.zope.org/Members/htrd/howto/FunctionTemplate
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist
if I get enough positive feedback from people who
actually use dtml-tree. (and a sufficently paranoid review would be nice
too.)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
2.2
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman
that much easier.
Im not sure thats true. Having less strict version requirements means that
there will be *more* *people* doing the development, support, and bug fixing.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev
confirmation that you are all happy with this combination of patches.
thanks,
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross
grows with the number of
threads - is this true?
yes
Cheers
I hope this helps
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
in a way that lead to strange behavior. 2.6 is more predictable, and
understandable.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
On Sunday 26 January 2003 7:25 pm, Kazuya FUKAMACHI wrote:
On Tue, 14 Jan 2003 10:33:40 +
Toby Dickenson [EMAIL PROTECTED] wrote:
I am currently looking at getting this into 2.6.1 or 2.6.2. I would
appreciate confirmation that you are all happy with this combination of
patches.
Have
schedule since December has been that this is imminent any
day now. I have some important bug fixes that I would like to include in
2.6.1, and I would like some assurance that beta 2 will not be released
mid-merge.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
random number.
self._p_changed = 1
return self.__random.random()
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo
/patch/Zope261b.patch
Thanks to everyone who has helped on this. This patch is in cvs ready for
2.6.1 beta 2.
Please give the beta a good work out.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL
On Wednesday 29 January 2003 8:50 pm, Brian Lloyd wrote:
(I saw Toby had committed some things, and it looks
like that merge is complete).
Yes, that is complete
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev
transaction to the next inside the exception and traceback.
The same applies to your prorosed fix. Is there a need to allow the error
handling transaction to commit? I propose it always be aborted.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
transaction.begin is:
'''Begin a new transaction.
This aborts any transaction in progres.
'''
(I should have a chance to experiment with this tomorrow)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope
On Monday 10 February 2003 8:47 pm, Shane Hathaway wrote:
Great, so there's at least 133 things to examine to see if they
could catch a ConflictError. And I only wrote about 15 of those.
The rest could be very time-consuming to audit.
tal:on-error also catches all exceptions. It could
of bytes sent back to the
client?
;-)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists
application state revert mid-request to the pre-transaction state seems
like a bad idea. Commiting application changes made in the second half of the
request seems bad too.
(All from theory - I ve not tested this)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
proxy. Set up a squid acl to catch this one
user, and send his requests via tcpwatch (or similar) rather than direct to
zope.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
commands on recovery. There is no
way to apply transactional semantics to application logic, except by cramming
all the work into one big command object.
(I hope that helps. Appologies in advance for any inaccuracies)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
components. I would be interested in your thoughts on whether this makes
a difference.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross
security issues in a *fork* starting with the 2.6 maintenance
branch?
(reply-to set to zope-dev)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
is secure
(Note that I dont consider this a flaw in Zope.)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
that are likely
to change early in the transaction.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related
On Tuesday 18 March 2003 3:24 pm, Chris McDonough wrote:
Our live sessions code uses the sessions about half to two-thirds of the
way through the transaction. Given what can happen in that first half,
there is easily plenty of time for read conflicts. I think I might be
able to move our
that will cause a POSKeyError when read. Can the
problem be reproduced using DirectoryStorage? (without the low consistency
connection)
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
case? I
am hoping that there may be a better solution that avoids the problems I
raised.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
are
non-persistent, otherwise bad zodb-level things can happen. Does Zope 3 guard
against this?
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope
type that I'd like to use revisions for.
The accepted wisdom is that feature like this should be implemented in the
application, above zodb. This has come up a few times on zodb-dev list.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
a port that ignored cookies but always used a specific
Version would avoid many of the existing problems too.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman
cant afford to stop using versions
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickensonIndex: lib/python/ZODB/ZApplication.py
===
RCS file: /cvs-repository/Zope/lib/python/ZODB/ZApplication.py,v
retrieving revision 1.13
On Tuesday 10 June 2003 09:32, Jamie Heilman wrote:
Toby Dickenson wrote:
! # Disable nasty insecure version support. Thanks to
! # Jamie Heilman and everyone one zope-dev
Unless you're damning me with faint praise for posting an exploit,
(which is fine)
No criticism
to allow them to
hook into the global gui; either the top bar or Control_Panel.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross
On Monday 16 June 2003 08:05, Toby Dickenson wrote:
On Saturday 14 June 2003 16:53, Christian Theune wrote:
When catching up with the mail in the mailinglist, I remembered a small
annoyance I'm having with the ZMI. I really appreciate the errorlog and
am using it frequently. But if you
you tested it?
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http
, for example as a seach page.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http
stuff as a non-root user. Portage
was designed to allow this, but I doubt it is well exercised. Trying this has
been on my to-do list for a while.
--
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson
___
Zope-Dev maillist - [EMAIL
?
--
Toby Dickenson - http://www.geminidataloggers.com/people/tdickenson
Want a job like mine? http://www.geminidataloggers.com/jobs for Software
Engineering jobs at Gemini Data Loggers in Chichester, West Sussex, England
___
Zope-Dev maillist
to
these functions?
--
Toby Dickenson - http://www.geminidataloggers.com/people/tdickenson
Want a job like mine? http://www.geminidataloggers.com/jobs for Software
Engineering jobs at Gemini Data Loggers in Chichester, West Sussex, England
___
Zope-Dev maillist
processed
normally.
I havent seen a mention of ulimit or autolance earlier in this thread They
are mostly adequate protection against the work problems.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman
, of course)
I'm also keen for users to nto
get MemoryErrors, but to just have their request take much longer ( cache
thrashing and the like...)
use squid, and it will retry the request.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
On Thursday 11 September 2003 03:03, John Barratt wrote:
I think ghosts
are only 'removed' after a restart,
fyi, ghosts are removed from memory using reference counting.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
On Thursday 25 September 2003 11:51, Chris Withers wrote:
Hmmm, does _p_deactivate() clear the contents of the object's _v_
variables?
Yes
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope
On Friday 26 September 2003 09:32, Chris Withers wrote:
Toby Dickenson wrote:
On Thursday 25 September 2003 11:51, Chris Withers wrote:
Hmmm, does _p_deactivate() clear the contents of the object's _v_
variables?
Yes
Then given your earlier comment that _v_ variables are supposed
. If you've got a current CVS checkout of Zope
I'm unable to test because of the Python 2.2 requirement :-(
Im in the same position, also :-(
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
On Friday 03 October 2003 15:33, Chris McDonough wrote:
Jim is keen to get an audit going quickly before a 2.7
final release, and the audit would be performed against Python 2.3.2.
Does anyone else have an interest in blessing Zope 2.6.x with Python 2.2/2.3 ?
--
Toby Dickenson
be cleared until the end of
the transaction?
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo
On Friday 10 October 2003 18:34, Dieter Maurer wrote:
Toby Dickenson wrote at 2003-10-10 07:54 +0100:
...
A while ago there was a discussion on zodb-dev about _v_-like attributes
that would be automatically cleared at the end of a transaction. Do we
need something similar
boundaries.
Agreed. Are there any situations, apart from the already discussed CMF
skindata, where this currently isn't the case?
every database adapter?
(I guess, but havent checked)
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
.
Apart from the most trivial cases, it would allow _v_ attributes to disappear
at random. Its a similar problem to the one that makes it hard to write an
optimiser for python code, and I am unconvinced that this is sane.
--
Toby Dickenson
___
Zope-Dev
thereafter.
If you are seening that then I think you need a bigger cache. And possibly
fewer publisher threads.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
one if nobody complains.
consider this a complaint. character encodings should be applied at zopes
boundary, not in the middle of its processing.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope
On Thursday 23 October 2003 08:07, Chris Withers wrote:
Toby Dickenson wrote:
Apart from the most trivial cases, it would allow _v_ attributes to
disappear at random. Its a similar problem to the one that makes it hard
to write an optimiser for python code, and I am unconvinced
On Tuesday 21 October 2003 18:08, Jens Vagelpohl wrote:
Just a quick heads-up:
Then we will start restoring the data
from the old drives.
That makes me nervous. How will you know that the sources in cvs havent been
compromised?
--
Toby Dickenson
On Thursday 23 October 2003 18:52, Chris Withers wrote:
What in the ZODB cache or other ZODB code could be causing _v_ variables to
stick around after they've been set to None in their containing objects?
reference cycles
--
Toby Dickenson
equivalent to getattr(some_object, id). Its
not obvious to me how this can be cleanly resolved in zope 2.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
these problems early
enough to fix the damage cheaply.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org
)
that didn't have to add the slash. What was the rationale
originally?
Because
dtml-var BASEPATH1/dtml-var absolute_url(1)
looks nicer than without the slash
?
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman
On Tuesday 09 December 2003 16:24, Evan Simpson wrote:
Summary: absolute_url(1)
Looks good.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
in front of your zope, then squid will manange both
HTTP 1.1 persistent connections to your browsers, and persistent connections
to your Zope.
The squid-to-zope persistent connections are not in the style of HTTP 1.1
though. Squid uses slightly different headers - I forget the details.
--
Toby
with my Formulator hack solution.
Can you point me to a desicription of this hack please.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related
to imagine why, since it
will get called whenever the object is ghostified, and has nothing
to do with the object's actual lifetime), don't reference any
persistent objects (and esp. not self) within it.
or 2b as jeremy suggested, put your __del__ on a non-persistent sub object.
--
Toby
On Monday 26 January 2004 12:08, Thyb wrote:
What could be the problem?
That indicates that you are out of memory. If that doesnt seem right, maybe
your storage is corrupt in a manner that the unpickler interprets as
something with a huge memory footprint.
--
Toby Dickenson
On Monday 26 January 2004 17:22, Tim Peters wrote:
It's actually that the number of __del__-resurrecting objects *plus* the
number of non-ghostifiable objects in cache is larger than the cache target
size, right?
Yes, Right. That is more achievable than I thought.
--
Toby Dickenson
On Tuesday 27 January 2004 19:08, Tim Peters wrote:
Maybe Toby remembers which release(s) of ZODB the
current cache implementation first appeared in
Zope 2.6
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org
of these troublesome objects that move themselves
to the top of the LRU list *during* the scan will end up *after* the scan
terminator node, and therefore do not get rescanned.
This works for me on 2.6, which is the only branch Im set up to use at the
moment.
--
Toby Dickenson
? diff
? diff2
Index
backlog. might
work.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http
on different Zope instances.
(my apologies if this is obvious)
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org
if
it crashes.
the others are all threads of one process. one main medusa thread, and 4
publisher threads.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
; basically do away with the Medusa request queue altogether and
use listen()'s backlog instead.
Last week you were keen that medusa keep processing requests so that it can
return a 503 error quickly. I guess your view on that requirement has
changed?
--
Toby Dickenson
applications that send emails in error handlers. MailHost isnt
transactional today, but Ive always wanted it to be.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
On Monday 15 March 2004 12:59, Darshan Preet Singh Manku wrote:
file = 'C:\tmp'
try 'C:/tmp' or 'C:\\tmp'. unless your file name really does contain a tab
character ;-)
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http
the
number of worker threads lets you increase the per-thread cache size.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http
;-)
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org
in this way, but it seems to
be how the Unicode support in Zope 2 was meant to be used.
That is correct.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
in
a filesystem or zodb database). Can you give some examples?
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org
using a BTree
of some kind.
--
Toby Dickenson
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
and change suggestions. In particular, my notes on using squid with
zope, and the changes I originally drafted for the Zope Developers Guide on
using unicode in Zope.
Is there now a more approporiate place to hold this documentation where it can
be maintained?
Thanks in advance,
--
Toby
301 - 381 of 381 matches
Mail list logo