#6255: need of an 'afterStartup' controller callback function
-------------------------------+--------------------------------------------
Reporter: robustsolution | Owner:
Type: Enhancement | Status: closed
Priority: Medium | Milestone: 1.2.x.x
Component: Controller | Version: 1.2 Final
Severity: Normal | Resolution: wontfix
Keywords: | Php_version: n/a
Cake_version: 1.2.2.8120 |
-------------------------------+--------------------------------------------
Changes (by mark_story):
* status: new => closed
* resolution: => wontfix
Comment:
I think we have plenty of callbacks as it stands. What is an example of
what you would do in this afterStartup() method? Your controller should
not need to know the state of the components, you create an unnecessary
level of coupling between controllers and components by doing this.
Perhaps you should be moving some of your startup() logic into your
initialize() and allowing beforeFilter() to handle this afterStartup()
logic.
Adding one more callback onto the existing two will not solve anything in
my opinion.
--
Ticket URL: <https://trac.cakephp.org/ticket/6255#comment:1>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC.
Our primary goal is to provide a structured framework that enables PHP users at
all levels to rapidly develop robust web applications, without any loss to
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---
