The advantage of the last form (below), is that you can use
acquisition, and don't need to know whether the variable came from the
session or from elsewhere. If you *really* want it to come from the
session only, you can always add the "only" tag to the dtml-with call.

In conjunction with this, it might be nice to have a special call that
sets the variable, if defined by acquisition, in the session. Something
like <dtml-call "sessionmanager.getSessionData.set('a')"> would set "a"
to the acquired value for "a", leave it undefined if not defined, and
not change it if it was not acquirable elsewhere (the acquired value
would take precedence over the session value).

Even better would be if I could just say <dtml-call
"SESSION.set('a')">.

Bob

--- Chris McDonough <[EMAIL PROTECTED]> wrote:

> A potential rhythm, however, might look like:
> 
>   <dtml-with sessionmanager>
>     <dtml-with getSessionData>
>       <dtml-call "set('a', 'b')">
>     </dtml-with>
>   </dtml-with>
> 
>    and
> 
>   <dtml-with sessionmanager>
>     <dtml-with getSessionData>
>       <dtml-var a>
>     </dtml-with>
>   </dtml-with>
> 
> I sorta like it the original way now that I've written that down. 
> :-)  It's
> easier to explain, AFAICS.
> 
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/

_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to