You mean should you learn an entire new framework so that you could have one layer less :D
Whenever I get such projects the temptation is strong to go with some of the so called REST api frameworks but I keep coming back to cake for the familiarity and flexibility. Imaging if you did want a V layer at a later date... Just my 2c T On Mon, Sep 22, 2014 at 2:27 PM, Jeremy Burns <[email protected]> wrote: > Canvassing some opinion... > > I'm just about to start a project that has an Angular and/or Polymer web > components front end, so the API only ever needs to send JSON responses and > receive normal posts/get requests. As such, there is no need for the 'V' > part of an MVC framework. I know CakePHP can do this very well (I've > already built one) but is it still considered the best/an ideal framework > for this purpose? > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/cake-php. > For more options, visit https://groups.google.com/d/optout. > -- ============================================================= Hire a CakePHP dev team : http://sanisoft.com ============================================================= -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
