Thanks 100rk, you pretty much answered all I needed to know. Just realized that the Cookie overhead per request is just not worth it. Best use Sessions and scale them across multiple servers appropriately when the need arises.
Your suggested solutions to getting it to use Cookies instead of Sessions were far more elegant than mine too, thanks! But for now I think I'll run it the Cake way and stick to Sessions. On Jan 18, 4:30 am, 100rk <[email protected]> wrote: > Generally, cookies are not designed to be overused (many cookies or > large datasets stored in them), they are being sent to the server > along with every request. > > If you _really_ want to substitute SessionComponent in whole > application with CookieComponent, try to remap used class: > > class AppController extends Controller { > public $components = array( > 'Session' => array('className' => 'Cookie'), > 'Auth' => array( > ... > > - their read/write/delete api is the same, so it _could_ work, as a > workaround, maybe (IDK for sure). -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
