If the methods are REALLY similar (like different variables being
plugged in from the url) then you can refactor to use the routing to
have both urls point to one method and then extract the data that's
different from the request object.
brian
On 9/10/07, Shekar C Reddy <[EMAIL PROTECTED]> wrote:
> The __call() magic method.
>
>
>
>
> On 9/10/07, ArticSun <[EMAIL PROTECTED]> wrote:
> >
> > Hi all!
> >
> > I got a controller with several methods like "option1Action",
> > "option2Action" etc. These methods are very similar but they're called
> with
> > different urls ("url/controller/option1", "url/controller/option2", etc.).
> >
> > My question is, if it is possible to have a default "method" which is
> called
> > when a certain method is not found? Some kind of autoload, but then for
> > methods instead of objects?
> >
> > How could I solve this?
> >
> > Thanks!
> > --
> > View this message in context:
> http://www.nabble.com/Default-method-in-controllers--tf4413945s16154.html#a12590869
> > Sent from the Zend Framework mailing list archive at Nabble.com.
> >
> >
>
>
