Progress update on using Symfony as API with frontend dealt with elsewhere.
It is working surprising well. The MVC aspect of Symfony makes creating REST web services easy and the View layer helps return the data nicely formatted. Symfony has been well suited to this approach. -Simon On Sep 29, 7:15 pm, Simon Cast <[email protected]> wrote: > Hi, > > Thanks for the info. > > Having read the manual some more along with the Jobeet Tutorial it > seems the best way to do this is to use the full Symfony MVC but > instead of rendering HTML render JSON/XML. > > http://www.symfony-project.org/jobeet/1_2/Doctrine/en/16 > > Regards, > > Simon > > On Sep 28, 5:09 pm, Eno <[email protected]> wrote: > > > On Mon, 28 Sep 2009,SimonCast wrote: > > > One pitfall that I haven't resolved is how the HTML/JS pages and > > > Symfony are going to site on the same server and play nice together. > > > I could see problems with going towww.example.comandSymfony > > > index.php taking over but that is probably resolved by changing the > > > htmldocs directory. > > > You can edit the .htaccess file and specify which URLs should not go to > > the symfony controller... > > > > On a similar note, does anyone know if there will be problems with > > > calling actions straight without first going through the index.php? > > > Since the controller sets variables, loads configuration, and creates the > > context, you would have to do that yourself if you are not using the > > symfony controller. > > > -- -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=.
