The old security framework had an authorizeOperation method that had enough information to be able to inspect and modify an OQL string before it would be executed. That whole framework is now deprecated, but I feel like it's a really powerful feature being able to modify OQL in such a way as to support adding some kind of security column to the where clause so you can implement row-level security on queries.
My question is, are the new securityManager and the old AccessControl interface able to both be used together or are they mutually exclusive? -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: +1-631-835-4771
