[wp-trac] [WordPress Trac] #12935: Evolve the URL routing system

[WordPress Trac]

#12935: Evolve the URL routing system
--------------------------+-----------------------------
 Reporter:  mikeschinkel  |       Owner:  ryan
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Permalinks    |     Version:  3.0
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------

Comment (by scribu):

 Replying to [comment:62 mikeschinkel]:
 > Replying to [comment:60 scribu]:
 > > But the perceived lack of flexibility of WP_Rewrite isn't due to
 regexes, but due to the way these patterns are generated and stored.
 >
 > You misquote me.  It's not a lack of flexibility of regular expressions;
 it's the requirement to match each URL in it's entirety that makes it very
 difficult for most people to set URL routes for anything beyond trivial.

 I didn't quote you to begin with.

 > Also, can you help me understand why you'd advocate maintaining a system
 that generates and map upwards of 1000 regular expresssions for a complex
 CMS when with a tree structure the matching would be 1 to 2 orders of
 magnitude less per page load?

 I advocate maitaining this system for normal use. Complex CMSs can do tree
 structure matching, as needed.

 > And please address why retaining the complexity of the regular
 expressions as used in the rewrite system makes sense vs. much more
 straightforward simple match rules that mere mortals are much more likely
 to understand (with fallback to RegEx, of course?)

 The system you propose is not actually that simple at all. You just
 replace the regex engine with PHP code, removing one common skillset with
 a very specific one (knowing the tree structure API and algorhitm).

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12935#comment:63>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software