Hi!
As of Zope 2.8.2 (http://svn.zope.org/?rev=38738view=rev) the '@'
character is allowed in object IDs.
Zope 3 does not allow object IDs starting with '@' because those names
are reserved for views.
Five makes Zope 3 style views available in Zope 2, so IDs starting with
'@' should be
yuppie wrote:
Hi!
As of Zope 2.8.2 (http://svn.zope.org/?rev=38738view=rev) the '@'
character is allowed in object IDs.
Zope 3 does not allow object IDs starting with '@' because those names
are reserved for views.
Five makes Zope 3 style views available in Zope 2, so IDs starting with
Max M wrote:
yuppie wrote:
As of Zope 2.8.2 (http://svn.zope.org/?rev=38738view=rev) the '@'
character is allowed in object IDs.
Zope 3 does not allow object IDs starting with '@' because those names
are reserved for views.
Five makes Zope 3 style views available in Zope 2, so IDs starting
yuppie wrote at 2006-3-10 12:14 +0100:
As of Zope 2.8.2 (http://svn.zope.org/?rev=38738view=rev) the '@'
character is allowed in object IDs.
Zope 3 does not allow object IDs starting with '@' because those names
are reserved for views.
Five makes Zope 3 style views available in Zope 2, so IDs
Dieter Maurer wrote:
yuppie wrote at 2006-3-10 12:14 +0100:
As of Zope 2.8.2 (http://svn.zope.org/?rev=38738view=rev) the '@'
character is allowed in object IDs.
Zope 3 does not allow object IDs starting with '@' because those names
are reserved for views.
Five makes Zope 3 style views
yuppie wrote:
Dieter Maurer wrote:
To support WebDAV as widely as possible, I would prefer to
get rid of all id restrictions. I do not like to see
new restrictions emerging...
You just don't like it or do you know a better alternative?
We need a way to make sure that object IDs can't mask
