---- Original Message -----
From: "Perrin Harkins" <[EMAIL PROTECTED]>
Maybe the flaw is that A:S:M should work like the standard memcached
model -- it should check for session data in the memcached dbase, and if
it
is not there, check the dbase for it...
That would be a much more reasonable model to use. You would have to
write all updates to both places.
Yes i think that A:S:M is a good idea in concept, but it seems that the
solution would be to have it work the way you are suppose to use
memcached -- then it would be a great asset actually... It might take a
performance hit -- but i guess for reads it would be great -- only writes
would be an issue.
-John
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
