What Amit is proposing with his
{% render partialURL%}
tag is extremely similar in concept to the
{% include_url %}/url/with/{{ param }}/{% end_include_url %}
tag that I proposed (and provided code for above). my reasoning for
using separate start and end tags was to ease the construction of a url
with variables. Otherwise they are identical in concept.
I'm not sure though if Amit envisaged resolving his partialURL using a
urlconf or some other mechanism.
Also note that my proof of concept code does actually construct a dummy
request, as contrary to what Amit implies, the request is not currently
available in DjangoContext (although it does take the user from
DjangoContext if it's available). This issue may be addressed in future
if the proposal for request processors is adopted (ticket #925).
The essence of my original post though was to solicit feedback as to
whether such an approach is a good one, or if there are better
alternatives for composing pages out of 'portlets' (or whatever you
want to call them).
