[development] Splitting hook_menu into hook_menu and hook_router

Dries Buytaert dries.buytaert at gmail.com
Fri Jan 19 13:33:43 UTC 2007

On 19 Jan 2007, at 10:28, Vladimir Zlatanov wrote:
>> While I'm not opposed to the idea, I still fail to see the big win.
>> Just because it provides logical separation or do you have a better
>> reason?

> Well... That is a reason enough in it's own right. Currently the menu
> hook has two concerns, menu placement and routing. While the init  
> could
> benefit from one place - it is simpler. The logic of what happens  
> later
> becomes too complicated leading to those annoying bugs/features like
> Access Denied for custom links in menu, etc...
> It is simpler, at least has the potential to be simpler, in my book  
> taht
> is better. Extra api? if the two apis are easier to understand than  
> the
> current one I think it is better.

I generally agree.  It looks promising but it does have some  
drawbacks/regressions.  It's difficult to weigh/evaluate these right  
now.  We'll have to take this a step further and experiment with it.   
I'm positive about the outcome.  :)

Dries Buytaert  ::  http://www.buytaert.net/

More information about the development mailing list