Cvars can of course hold complex values. WDDX is dirt simple to implement.
And you can forget about all locking issues. No duplicate to request scope and duplicate back, either. So cvars are arguably simpler to code and manage.
Thats the good side.
The bad side is of course that you're getting a db hit (its a poor soul indeed who stores cvars in the Registry, or cookies), and you have the aforementioned wddx overhead.
Then there's the fact that nowadays session vars can scale up to clusters, so the only real reason to use cvars is the failover issue? What with svars being in-memory should mean the server runs faster when load starts climbing, versus a db-oriented cvar.
All the plus-side stuff for switching to svars has been theoretical only for me so far. I have yet to have a site whose demand was high enough to make me consider switching.
--
-------------------------------------------
Matt Robertson, [EMAIL PROTECTED]
MSB Designs, Inc. http://mysecretbase.com
-------------------------------------------
--
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
