My favorite approach regarding the lock and security checking would be to use the event framework.
There could be something like a SecurityListener implementing all the relevant interfaces (ContentListener, StructureListener...) and performing the security checking. This would help to slim down the Slide core methods and would make the security and lockin stuff pluggable.
The listener can do the permission checking as well as invalidating the acl-cache.
I'd help to migrate the current code to an event based approach if appreciated.
Regards,
Daniel
Oliver Zeigermann schrieb:
I am currently thinking about how Slide could be made faster with little effort. As the main source of Slide being slow I identified method
public ObjectNode retrieve(SlideToken token, String strUri, boolean translateLastUriElement)
in StructureImpl and lock and securiy checks.
As I don't want to change much, maybe some sort of *direct* caching could do that maps the string Uri to the Object Node resp. to locking and security data. It would, however, be complicated to determine which calls to Slide invalidate the entries.
Any ideas? Comments?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
