> I'm not sure if restricting Ask functionality is along the lines of > Wikipedia policies - it's not a modification operation therefore it should > be public, I believe. Sure, but my MW sites aren't wikipedia. Also, imagine how much resourse intensive would it be on the huge datasets with lots of properties and property values defined.
> I agree, that abuse bocking and request throttling might be a solution here, > but in general, I wouldn't recommend restriction of access, but a > functionality instead, e.g. limited amount of joins or something like that. Maybe you're right. It would be nice to have the settings mentioned by Markus $smwgQSubpropertyDepth, $smwgQEqualitySupport separately for anonymous and the rest of the users. The problem is, that such queries might be unavailable sometimes. > This kind of actions is generally hard to limit and predict therefore it's > quite easy to abuse. This might be a serious bottleneck in SMW adoption by > Wikipedia. Dmitriy ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
