As of Zope 2.8.2 (http://svn.zope.org/?rev=38738&view=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 disallowed in Zope 2 as well.
If there are no objections I'll fix that in Zope 2.8, 2.9 and trunk.
There are several use cases for using an email as the user id.
Especially when integrating to legacy systems.
So http://localhost/plone/Members/[EMAIL PROTECTED] should be legal.
Otherwise it is a pita. (Until it gets ok to it in Plone I have a
monkeypatch for Plone that allows this, and it's pretty simple.)
If you just want to prohibit "id.startswith('@')" it is fine by me.
But prohibiting "id.find('@') != -1" would suck.
I cannot at the top of my head think of a case where @name is used...
But if anyone else knows about it. Please speak up.
hilsen/regards Max M, Denmark
IT's Mad Science
Phone: +45 66 11 84 94
Mobile: +45 29 93 42 96
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -