"Phillip J. Eby" wrote:
Nope. The two levels of methods (get/retrieve and new/create) are there to
seperate Rack-level concerns from implementation concerns. getItem() and
newItem() handle maintenance of Rack-level invariants such as the retrieval
cache, while retrieveItem() and
At 11:54 AM 6/27/00 +0400, Jephte CLAIN wrote:
mike wrote:
There is no way to infinite recursion if Rack.getItem is leaved
untouched.
Ah ah. But people will touch it. Like me for example :-)
There is no way to prevent overriding getItem from a ZClass for example.
And it *will* recurse
hello,
Rack.createItem (low level method) first calls Rack.getItem (higher
level method) to check the existence of the item.
This causes infinite loop in certain cases. It should (IMHO) call
Rack.retrieveItem instead
regards,
jephte clain
[EMAIL PROTECTED]
Jephte CLAIN wrote:
hello,
Rack.createItem (low level method) first calls Rack.getItem (higher
level method) to check the existence of the item.
This causes infinite loop in certain cases. It should (IMHO) call
Rack.retrieveItem instead
Could you provide an example please?
Mike
