On 2008-04-17 09:04:06 -0700, mike wrote: > On 4/17/08, Peter J. Holzer <[EMAIL PROTECTED]> wrote: > > But in that case I'd use a different scheme: Tell your users to choose a > > hard to guess prefix (for example, 16 random letters or digits) for > > their keys. This will ensure that users cannot read or modify each > > other's data unless they are told or can guess the prefix. > > thats originally how i was going to do it, except people can wreak > havoc by issuing flush_all and such. depending on how many people use > it, it could wreck the whole point of having the cache there...
I didn't think of flush_all. Yes, that's nasty in a multi-user
environment. I thought of adding a warning that users can affect each
other negatively by either caching lots of data, or storing lots of data
in unusual sizes. But there isn't much you can do about that if you
share one cache between several users and it isn't that different to
what users can do to each other with shared hosting anyway.
hp
--
_ | Peter J. Holzer | It took a genius to create [TeX],
|_|_) | Sysadmin WSR | and it takes a genius to maintain it.
| | | [EMAIL PROTECTED] | That's not engineering, that's art.
__/ | http://www.hjp.at/ | -- David Kastrup in comp.text.tex
signature.asc
Description: Digital signature
