I think I have a simple question about how Zope is handling requests. My
current task is to understand an already-written Zope web application.
One thing I can't wrap my head around is this URL:
https://mysite.com/UserManagement/Users/asmithS/
Speaking in Zope terms, the UserManagement object i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2012 12:55 PM, Jared Hall wrote:
> I think I have a simple question about how Zope is handling requests.
> My current task is to understand an already-written Zope web
> application.
>
> One thing I can't wrap my head around is this URL:
>
>
Ok I'd read about those functions a little bit in the Zope 2 book or the
Developer's Guide, but they seemed like advanced techniques that I probably
wouldn't need to understand.
Back on topic; I ran this awesome command in the terminal:
grep getitem x=$(find . *.*)
and turned up some random re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/23/2012 03:01 PM, Jared Hall wrote:
> Ok I'd read about those functions a little bit in the Zope 2 book or
> the Developer's Guide, but they seemed like advanced techniques that I
> probably wouldn't need to understand.
>
> Back on topic; I ran
I don't know why these are creating new threads. And I'm sorry for the
formatting on that last message.
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://ma
Tres, I see what you mean. You're saying that the object lookup for a request
follows a pattern and that the __getitem__ function has a role in that pattern.
That's fine, but even if this is returning a User object there is still a
problem. I think we're beyond the point where you can help me th
