No subject

Wed Jul 11 09:24:25 UTC 2012

<td valign=3D"top" tal:content=3D"here/LastName">Doe</td>

What I want to know is: How can do these URL arguments work? A more advance=
d question would be: how do you think these here/*** variables are being ad=
ded to the context.

I'm actually using Zope 2.

Thanks for any help

Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; "><span class=3D"Apple-style=
-span" style=3D"border-collapse: collapse; color: rgb(34, 34, 34); font-fam=
ily: arial, sans-serif; font-size: 13px; ">I think I have a simple question=
 about how Zope is handling requests. My current task is to understand an a=
lready-written Zope web application.<div><br></div><div>One thing I can't w=
rap my head around is this URL:<div><br></div><div><a href=3D"https://mysit=" target=3D"_blank" style=3D"color: rgb(=
17, 85, 204); "><wbr>UserManagement/Users/asmithS/</a></=
div><div><br></div><div>Speaking in Zope terms, the UserManagement object i=
s contained in the top-level product. In the UserManagement object, there i=
s a Users object. That's all fine and dandy, run of the mill, acquisition/c=
ontainment. However, the Users object has no asmithS object. In fact, asmit=
hS is just a username, which makes the last field in the URL essentially a =
parmeter on the Users object.</div><div><br></div><div>From examining the b=
ehavior of the webapp and the code itself, I know that the index_html metho=
d of the Users object is what is returned from this request, which is a Pag=
e Template that displays the user information based on the parameter.</div>=
<div><br></div><div>All of what I've said so far could be wrong, so feel fr=
ee to correct me if I've mis-spoken. The problem I have is that this asmith=
S guy seems magical. I can't figure out how the index_html knows to be call=
ed with the username as a parameter(obviously the index_html function doesn=
't explicitly require the parameter).</div><div><br></div><div>What I BELIE=
VE is happening: the asmithS argument is processed before the page template=
 renders. For example, when asmithS is given, a lookup is performed on the =
database that adds variables to the REQUEST object such as FirstName, LastN=
ame, etc. I can't find this happening but I think it must exist.</div></div=
><div><br></div><div>From the zpt file:</div><div><br></div><div>&lt;td val=
ign=3D"top" tal:content=3D"here/LastName"&gt;<wbr>Doe&lt;/td&gt;</div><div>=
<br></div><div>What I want to know is: How can do these URL arguments work?=
 A more advanced question would be: how do you think these here/*** variabl=
es are being added to the context.</div><div><br></div><div>I'm actually us=
ing Zope 2.</div><div><br></div><div>Thanks for any help</div></span></body=


More information about the Zope mailing list