I need some advice on some architecture for a website.

I am in charge of running a pretty significantly high traffic sites (3
sites that get around 400+ req. per sec at peek hours). The site was
started a long time and and the architecture was not maintained very
well throughout the years. There is no framework in place as of now.
It's all static.

We have decided to try out using a cake framework for a couple project
to see if this will provide the speed we are looking for.

The problem develops when trying to "integrate" cake with the current
website. The website as of now is static. http://www.example.com/story
- There is a folder "story" in the root of htdocs. There is a lot of
dynamic database calls with parameters, but the entire site (thousands
and thousands of pages) is developed this way.

I would like to start integrating cake in, but I don't see a way of
doing this without causing a problem with the current site
architecture.

All of our servers are in house so having a "custom" install of cake
is not a big deal. Basically I'm looking for a way to have http:/
www.example.com/onsale use cake, without touching the root, or other
directories (http://www.example.com/story) that are not written in
cake.

One idea I had was creating a new user and setting up a subdomain
(http://cake.example.com). Then using .htaccess to rewrite (http://
www.example.com/onsale) to (http://cake.example.com/onsale). If this
was all done through mod_rewrite I could keep the (http://
cake.example.com) url's private... but I'm not sure.

Any other suggestions?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" 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/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to