We’re currently sitting on a Symfony 1.4 implementation of our system. The system is too big to re-develop in Symfony 2 and to an over-night-switchover – the re-dev will take us probably a year. What we are thinking of doing, is to install a new Symfony 2 project which is blank, except for one task – pass-through!
The idea is that your browser ask for example.com/products… the Symfony 2 installation recognizes that it has to actually ask the old system, and it does curl or something similar to go and ask the old server on Symfony 1.4 the same question, let’s say old.example.com/products… whatever that server response with (headers, cookies, etc) gets parsed by the Symfony 2 server and passed back to the browser. The browser then are none the wiser that he’s actually talking to a “proxy”.
We then re-develop the module called “products” in Symfony 2 and when we roll out we merely switch proxying “off” for that module. This way we stick to iterative development and we make the impact and learning curve much better on the dev team (and off course on the business).
I’ve contemplated mod_proxy in apache, I’ve thought of installing a different proxying server, but the above solution would suite us best.
Problem is, I know Fabio have done this for, I think it was vimeo.com (or some other video site) but I can’t find any documentation or tutorials on how this was achieved and where I should concentrate in my research.
What you’re describing could be accomplished using
mod_rewrite. Create conditions for each of these modules and rewrite them to the appropriate front controller.