Hello Lukas ! Actually, when a user browse my (imaginary) application, his HTTP requests would be sent to the Presentation tier (PRES). On PRES, the routing part would be done. Then PRES would send over the wire (with a SOAP request) the Symfony2 context to the Application tier (APPS). [I believe that the Dependency Injection Container is precisely this context containing session parameters, GET and POST, etc...] APPS would run the controller code (business logic and data retrieval) and then would send back (over the wire with the SOAP response) to PRES every piece of information needed to choose the view to be rendered using template variables. Finally PRES would sent the HTTP response back to the user.
I know it's not possible with the current code, but i believe Symfony2 is flexible enough to make it work out the box with a little work ! Regards, Benoît On 11 oct, 19:55, Lukas Kahwe Smith <[email protected]> wrote: > On 11.10.2010, at 16:38, Benoît wrote: > > > > > Hello guys ! > > > First of all, thank you for your messages. > > > Let's clarify my point of view: to me it's all about extending > > Symfony2 framework. > > > I don't want to have to write two different Symfony2 projects, one > > exposing REST API to the other. I want to be able to write one project > > and decide as late as possible how to deploy it. It could be great to > > be able to configure it as easily as the database access: single > > server or multitier architecture. > > > In other words, i don't want to implement a Service Oriented > > Architecture. By the way, in my company (a bank) Application tier is > > only accessible by Presentation tier. I just want to be able to use > > Symfony2 in a more flexible way to comply with my company > > recommendation, which is to separate concerns for security reasons. > > Scaling is not the main purpose in my case (but can be in others). > > > The problem in PHP world is that there is no such thing as RMI to > > communicate between tiers. That's why I thought about SOAP. The goal > > is to extend Symfony2 framework by adding internal classes which > > implement a way to execute controller code remotely. The benefit of > > SOAP over standard RPC is the WSDL acting as a contract between tiers. > > It will be like defining a internal Symfony2 communication protocol. > > > After reading some Symfony2 code, it's not crystal clear for me what i > > have to modify to implement my proof of concept. That's why I'm asking > > you guys ! :) > > so what you want is that instead of the template parameters to be send to a > template right away .. you want the parameters to be serialized optionally to > be send over the wire and then deserialized and then handed over to a > template? > > this could be possible, but you would have to constrain yourself quite a bit > and add some stuff here and there. i dont think its really feasible to try > and make this work out of the box. > > regards, > Lukas Kahwe Smith > [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en
