Sorry, but it is hard to understand what you need without asking... Why to use symfony only to manage API calls? Symfony strength, IMO, is the controller / context / configuration layer. And there is also the view layer. But there is no standard Facade or Service layer and the DB is managed by doctrine or propel. Maybe you can use only one of them?
Anyway I will say how I do. I use a JS template engine ( http://embeddedjs.com/getting_started.html) and most of the calls are done using ajax / json. So my symfony pages return json and js renders the html. Might be usefull or not. If you could explain your need a little better (forces / constraints) I think you would get a better focused help. 2009/9/28 Simon Cast <[email protected]> > > Hi, > > I'm working on a project where we are going to not use the presenation/ > view layer of symfony to render pages. All the actions, business > logic and database access will be handled by Symfony but the > presenation/page generation will be handled using straight HTML/JS > (don't ask). Symfony in effect manages API calls. > > Does any one have advice or tips on potential pitfalls? > > 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 to www.example.com and Symfony > index.php taking over but that is probably resolved by changing the > htmldocs directory. > > On a similar note, does anyone know if there will be problems with > calling actions straight without first going through the index.php? > > Thanks for any pointers. > > Regards, > > Simon > > > --~--~---------~--~----~------------~-------~--~----~ 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] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
