Paul Winkler wrote:
absolute_url

 - containment only, does not include contextual elements from the
   client's URL, that's the whole point of this method :-)


What do you mean by "contextual elements from the client's URL"

absolute_url(relative=1)
  - same as absolute_url, and not usable in some VHM situations.

But what's it for? What change does relative=1 make? Why is it not usuable in some situtations?


absolute_url_path
 - is usable with VHM, but still containment only.

virtual_url_path
 - is usable with VHM, but still containment only.

Again, what do both of these do?

getPhysicalPath
- containment only, not compatible with VHM at all and should NEVER
be used for URLs.

?! it certainyl works as inteneded with VHMs, what are you trying to say here?


request/URLx - close, but no cigar: leaves out traverse_subpath elements.

Really? Should it?

request/VIRTUAL_URL
- includes context and traverse_subpath elements, but doesn't work if a VHM is not present or is not triggered.

Interesting. What's wrong with just:

python:request.URL+'/'+'/'.join(request.traverse_subpath)+'?'+REQUEST.QUERY_STRING

?

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to