originated from but most e-mail clients discard custom headers but preserve
a 'In-Reply-To' header with the original message-id.
Don't count on it! :) I spent quite some time working on a full-text
mailing list search/archive system and one of the things I wanted to do
was preserve thread
Ken Manheimer wrote:
I'm not expert on eiffel or even interfaces, but my understanding having
interface "specification very near to the implementation" is misleading,
at best. The key thing is that there may be many implementations, all of
which should be written to the same implementation
How can I find out exactly what is causing my security permissioning to
fail.
I have put extra stuff into ZPublisher\BaseRequest.py at line 463 so I
know that I'm failing on
UnauthorizedYou are not authorized to access this resource.
URL='http://192.168.0.4:7080/live/index_html' No
C:\Python\devel\Zopecvs -z9 upd -A -P -d
CVS.EXE [update aborted]: connect to zope.org:2401 failed: Connection
refused
Am I pointing at the wrong server or something?
--
Robin Becker
___
Zope-Dev maillist - [EMAIL PROTECTED]
Lalo Martins wrote:
On Fri, Nov 24, 2000 at 08:11:48AM -0800, Michel Pelletier wrote:
Python Interface Proposal
I have been working on a proposal for enhancing the existing interface
documentation in Zope. The Wiki for this project can be found here:
As far as what's written on
Michel Pelletier wrote:
Lalo Martins wrote:
On Fri, Nov 24, 2000 at 08:11:48AM -0800, Michel Pelletier wrote:
Python Interface Proposal
I have been working on a proposal for enhancing the existing interface
documentation in Zope. The Wiki for this project can be found
Robin Becker wrote:
How can I find out exactly what is causing my security permissioning to
fail.
I have put extra stuff into ZPublisher\BaseRequest.py at line 463 so I
know that I'm failing on
UnauthorizedYou are not authorized to access this resource.
Dieter Maurer wrote:
Michel Pelletier writes:
Also, defining the interface seperately keep the two things apart,
impementation and interface, and doesn't allow you to sneak in a new
method unless you also sneak it into the interface, thus making a
stronger "contract" with the user.
Brett Carter wrote:
I have a folder with greater than 5000 ZClass instances in it. It
takes 5mins to do an objectValues for every object in the folder -
is there a higher perfomance call I could make?
-Brett
Standard folder performance degrades pretty quickly once you get
a lot of objects
On Tue, 28 Nov 2000, zope wrote:
Hi!
I am currently developing a tool for reverse engineering
ZClasses into UML using ObjectDomain and JPython.
this tool connects directly to a Zope instance and queries
the ZClass entities, methods and inheritance relations by
calling a set of
Hi Joachim !
Joachim Schmitz wrote:
I am currently developing a tool for reverse engineering
ZClasses into UML using ObjectDomain and JPython.
this tool connects directly to a Zope instance and queries
the ZClass entities, methods and inheritance relations by
calling a set of utility
Id recommend all the above but just for reference "objectIds" is faster than
"objectValues".
--
Andy McKay, Developer.
ActiveState.
- Original Message -
From: "Casey Duncan" [EMAIL PROTECTED]
To: "Brett Carter" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, November 28, 2000
Ok, I'll bite. Why doesn't the standard folder scale? Seems like a
design flaw to me - why doesn't the default folder use catalogs or BTrees?
-Brett
"Casey" == Casey Duncan [EMAIL PROTECTED] writes:
Casey Brett Carter wrote:
I have a folder with greater than 5000 ZClass instances
Brett Carter wrote:
Ok, I'll bite. Why doesn't the standard folder scale? Seems like a
design flaw to me - why doesn't the default folder use catalogs or BTrees?
-Brett
Because massive scale is not a requirment of folders, they are meant to
organize content for humans, not to be
To my mind it's the browser.
This is a simple trick I use when egating the caching in IE for instance.
Stick a space on the end of the url and IE thinks it's a new one but blindly
strips them before getting the same refreshed page.
This works with any server and any page on that server btw.
I've added a sub-proposal to the Interface proposal for describing
additional meta-data with Interface objects:
http://www.zope.org/Wikis/Interfaces/ExtesableMetaData
Please comment about this interesting possibility.
-Michel
___
Zope-Dev maillist
Brett Carter wrote:
Ok, I'll bite. Why doesn't the standard folder scale? Seems like a
design flaw to me - why doesn't the default folder use catalogs or BTrees?
-Brett
AFAIK a standard folder uses a linear search when you request an object from it
(ala Python dictionaries, someone please
Is security really a part of an object's interface? I thought this was more
of an implementation thing.
- Original Message -
From: "Michel Pelletier" [EMAIL PROTECTED]
To: "Geeks Mailing List" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, November 28, 2000 4:05 PM
Subject:
I notice you mention post/pre conditions (something that UML obviously talks
about). I wonder if we want to do a bit of research on Eiffle and it's
contractual description. The only thing I wonder is if some of this is
actually useful programatically, if that makes sense? It's great info,
On 11/28/00 4:05 PM, "Michel Pelletier" [EMAIL PROTECTED] wrote:
I've added a sub-proposal to the Interface proposal for describing
additional meta-data with Interface objects:
http://www.zope.org/Wikis/Interfaces/ExtesableMetaData
Please comment about this interesting possibility.
Chris McDonough wrote:
Is security really a part of an object's interface?
Maybe. Are examples? Also maybe. It's documentation, so specific
systems that use interfaces may want to be able to extend the kinds of
information they can associate with interface elements.
I thought this was
"Michel" == Michel Pelletier [EMAIL PROTECTED] writes:
Michel Because massive scale is not a requirment of folders, they
Michel are meant to organize content for humans, not to be
Michel large-collection containers. A folder with 5000 elements
Michel is not very useful to a
Robin Becker writes:
How can I find out exactly what is causing my security permissioning to
fail.
I have put extra stuff into ZPublisher\BaseRequest.py at line 463 so I
know that I'm failing on
UnauthorizedYou are not authorized to access this resource.
Michel Pelletier writes:
Dieter Maurer wrote:
Michel Pelletier writes:
Also, defining the interface seperately keep the two things apart,
impementation and interface, and doesn't allow you to sneak in a new
method unless you also sneak it into the interface, thus making a
Ken Manheimer writes:
Dieter Maurer wrote:
It is a very good thing to have the specification very near
to the implementation -- as a permanent guide to the
implementor. It is even better, when big parts of the
specification becomes part of the executable code
(as is the
Jim Fulton writes:
Dieter Maurer wrote:
I cannot see, why the separation of interface and implementation
should make the contract stronger.
The interface *is* the contract. If someone builds a house
for me, I don't want the house to *be* the contract. I want the
house to adhere
In article [EMAIL PROTECTED], Robin Becker
[EMAIL PROTECTED] writes
Apparently, your "live" is a Z instance.
It is quite easy to forget the ZClass permission mapping
(or get it wrong). This may lead to strange permission
problems.
Which ZClass permission mapping? Anonymous seems to be able
[Christopher Petrilli]
I notice you mention post/pre conditions (something that UML
obviously talks about). I wonder if we want to do a bit of
research on Eiffle and it's contractual description. The only
thing I wonder is if some of this is actually useful
programatically, if that makes
Hi,
I'm trying to figure out the right way to implement a set of classes
and roles in ZPatterns. I asked some questions about this a while
ago, and then went away and did some learning, but I'm stuck again
and I'm afraid I need to ask more questions.
I have two types of actors - Person (with
Jeffrey P Shell [EMAIL PROTECTED] said:
But I'm not sure how one would go about setting your meta-data in a way that
is at all natural to Python. I think that exceptions that a method
must\should raise *should* be part of a signature\contract. This is one of
the really cool things about Java.
Guido van Rossum [EMAIL PROTECTED] said:
When you've fully debugged an application, you turn both off.
When you've fully debugged a library module, you create two versions:
one with both turned off, for use in fully debugged applications, and
one with pre-conditions on and post-conditions off,
31 matches
Mail list logo
