Re: Net_URL_Mapper or Net_URL_Router (was:Re: [PEAR-DEV] [PEPr] Proposal finished Networking::Net_URL_Mapper)

On 3/1/07, Bertrand Mansion <golgote@mamasam.com> wrote:

Le 25 févr. 07 à 10:00, PEPr a écrit : PEPr has automatically finished the proposal on Networking::Net_URL_Mapper. Sum of Votes: 6 (2 conditional)

Result:       This proposal was accepted

Further details on the status of the proposal and the votes can be found here: http://pear.php.net/pepr/pepr-proposal-show.php?id=428 Hi, Obviously this package didn't drive a lot of interest although I believe it is a very useful addition to any programmer's toolset. Anyway, I consider not enough people voted for it to be added to PEAR. It's probably my mistake since documentation is a bit scarce at the moment.

Not that anyone cares about what I think ;-), but I feel like this would make a great addition. If people didn't like the name, they should not have voted +1 on it? But they did, so I guess it passed. The reason why some proposed renaming the package is because of how things are already "called" in other (MVC) frameworks. Take the Zend Framework as an example, it's referenced with Zend_Controller_Front::getRouter and the like. So people would probably search PEAR for "router" instead of "mapper". By the way, Rails does the same. I *think* Symfony is also following this model. What's your concern with renaming it? Cheers, Till