That's exactly what I was looking for.
Kevin H.
On 8/2/06, Kaan <[EMAIL PROTECTED]
> wrote:
Kevin Horn wrote:
> Can anyone point to an example of how the positional parameter support
> actually ended up working? I couldn't find anything on the wiki or through
> Google, except for trac ticket #73...which isn't very clear.
>
> Thx
>
> Kevin H
>
> On 8/1/06, anders pearson < [EMAIL PROTECTED]> wrote:
> >
> > On 2006-08-01 12:58:08 -0600, Eric Brunson wrote:
> >
> > > Fred,
> > >
> > > Thanks for the pointer to the article. I've been playing with TG, but
> > > haven't used it for a production application yet. I'm interested in the
> > > list's take on this statement:
> > >
> > > However, the Django configuration system allows for maximum control
> > > and flexibility. Django URLs can be easily remapped onto an
> > > application after a major refactoring. This helps prevent "link rot"
> > > caused by old bookmarks or cached search engine results. "Link rot"
> > > severely hurts the traffic levels and usability of content-based Web
> > > sites that Django was designed to create.
> > >
> > >
> > > Can't turbogears provide default handler that could be used to intercept
> > > "bad" or "old" links and redirect them into a newer or refactored
> > hierarchy?
> >
> > Yes. There's also Routes:
> >
> > http://routes.groovie.org/
> >
> > which is a port of the Rails routes system that lets you do all the
> > fancy mapping to support arbitrary URL schemes. Integrating it with TG
> > is pretty easy.
> >
> > I've used Routes a bit and I love it for supporting legacy url
> > schemes. However, the tradeoff is that it (and Django's regexp based
> > mapping) is very complicated and difficult to debug. If I don't have
> > to deal with legacy URLs, I'll go for the simple cherrypy approach
> > every time. The recent addition of positional parameter support in
> > TG has made it easy to support all but the most convoluted URL
> > structures now without introducing the complexity and confusion of
> > mapping.
> >
> > --
> > anders pearson : http://www.columbia.edu/~anders/
> > C C N M T L : http://www.ccnmtl.columbia.edu/
> > weblog : http://thraxil.org/
> >
> >
> >
>
> ------=_Part_100184_1495228.1154466153486
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 2820
>
> Can anyone point to an example of how the positional parameter support actually ended up working? I couldn't find anything on the wiki or through Google, except for trac ticket #73...which isn't very clear.<br><br>Thx<br>
> <br>Kevin H<br><br><div><span class="gmail_quote">On 8/1/06, <b class="gmail_sendername">anders pearson</b> <<a href="" href="mailto:[EMAIL PROTECTED]"> [EMAIL PROTECTED]">[EMAIL PROTECTED]</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> On 2006-08-01 12:58:08 -0600, Eric Brunson wrote:<br><br>> Fred,<br>><br>> Thanks for the pointer to the article. I've been playing with TG, but<br>> haven't used it for a production application yet. I'm interested in the
> <br>> list's take on this statement:<br>><br>> However, the Django configuration system allows for maximum control<br>> and flexibility. Django URLs can be easily remapped onto an<br>> application after a major refactoring. This helps prevent "link rot"
> <br>> caused by old bookmarks or cached search engine results. "Link rot"<br>> severely hurts the traffic levels and usability of content-based Web<br>> sites that Django was designed to create.
> <br>><br>><br>> Can't turbogears provide default handler that could be used to intercept<br>> "bad" or "old" links and redirect them into a newer or refactored hierarchy?<br><br>Yes. There's also Routes:
> <br><br> <a href="" href="http://routes.groovie.org/">http://routes.groovie.org/">http://routes.groovie.org/ </a><br><br>which is a port of the Rails routes system that lets you do all the<br>fancy mapping to support arbitrary URL schemes. Integrating it with TG
> <br>is pretty easy.<br><br>I've used Routes a bit and I love it for supporting legacy url<br>schemes. However, the tradeoff is that it (and Django's regexp based<br>mapping) is very complicated and difficult to debug. If I don't have
> <br>to deal with legacy URLs, I'll go for the simple cherrypy approach<br>every time. The recent addition of positional parameter support in<br>TG has made it easy to support all but the most convoluted URL<br>structures now without introducing the complexity and confusion of
> <br>mapping.<br><br>--<br>anders pearson : <a href="" href="http://www.columbia.edu/~anders/">http://www.columbia.edu/~anders/"> http://www.columbia.edu/~anders/</a><br> C C N M T L : <a href="" href="http://www.ccnmtl.columbia.edu/">http://www.ccnmtl.columbia.edu/"> http://www.ccnmtl.columbia.edu/</a><br>
> weblog : <a href="" href="http://thraxil.org/">http://thraxil.org/ ">http://thraxil.org/</a><br><br><br></blockquote></div><br>
>
> ------=_Part_100184_1495228.1154466153486--
http://www.cherrypy.org/trunk/docs/book/html/index.html#id3516454
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
