On May 15, 2007, at 8:56 AM, Chandra wrote:

>
> The company I work for has a PHP/MySQL (and the Smarty Template
> Framework as a front end) based website that been running for a little
> while....the time has come to add more functionality to the site.  I'd
> like to use use CakePHP to add these new features on...and I need to
> see if it's even possible (I'm a Cake newbie) and then need to sell it
> to my boss.  I was hoping somone could answer a few simple questions
> for me:
>
> 1.  Site Authentication is done using PHP sessions stored in a
> database...Can Cake use the same session methods or will the users
> have to re-authenticate as they pass between the old and new
> functionality (and vice-versa)

You might just want to read the cookies to get the session_id, and  
use a Cake model to grab the session data and craft a cake session  
using that data. I've done it before and it works great for SSO  
situations.

>
> 2.  There is some business logic and classes from the old site I need
> to use - anything to watch out for?

Divide be zero can be nasty. I wouldn't worry about null pointer  
exceptions, though. :) Just use include_once/require_once like you  
normally would. Sometimes it's nice to encase things in components/ 
helpers, but whatever suits you best.

>
> 3.  In accessing the existing MySQL database schema...I can use Cake's
> CRUD capabilities...or is there a alternate way I should be accessing
> the data?

Cake can do it. Give it a try with scaffolding to see how it will end  
up working for you. You may have to configure a few things if your  
schema isn't CakePHP naming convention compliant, though.

-- John

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" 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