WordPress.org

Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #16692, comment 14


Ignore:
Timestamp:
03/09/2011 01:42:31 AM (9 years ago)
Author:
mikeschinkel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16692, comment 14

    v1 v2  
    66The current `WP_Rewrite` system is overly complex because there is an impedance mismatch between the `WP_Rewrite` system ''(a list of regexes with almost no metadata)'' and the underlying use-case it is trying to model ''(a tree of nodes and leafs where each node and/or leaf potentially needs unique metadata based on it's parent path.)''
    77
    8  '''''The current `WP_Rewrite` system just does not ''"match"'' the underlying use-case'''  ''(pun intended)'' and as such just gets more and more complicated as requirements get added to WordPress. Isn't it time to think different?'' 
     8 '''''The current `WP_Rewrite` system just doesn't ''"match"'' the underlying use-case'''  ''(pun intended)'' and as such just gets more and more complicated as requirements get added to WordPress. Isn't it time to think different?'' 
    99
    1010A great analogy is that `WP_Rewrite` is like SOAP-based web services ''(i.e. overly complex)'' vs. a URL routing system that is analogous to REST-based web services ''(simple and elegant.)'' Implementing a match system within `WP_Rewrite` would make it harder to prove the value of an alternate approach in a plugin vs. embracing a straight replacement of `$wp->parse_request()`.