(architecturally I
find Slide a completely impossible act to follow. Which makes me a little shy).
I agree we really need *much* better developer docs. Will you be able to contribute anything describing your experience with Slide's internals? Maybe a starting point for better docs...
Sure. But - maybe it's an Australianism - I meant the architecture's great.
How ever this may be, better docs really are a *must*.
Which sort of begs the question, why not allow PROPFIND to
just call a
SEARCH, if appropriate? (And yes, I have got classes to generate a SEARCH body).
Which also raises the question, why is PROPFIND sooo slow?
Because of the architecture. Clean, and no shortcuts. (see the invocation tree).
As a starter, StructureImpl.getChildren() shouldn't be performed more than once for
the parent folder, but is done each time a child is retreived (ACL)
ComputedPropertyProvider.isSupportedProperty () should be cached.
Performance notes: Even when PROPFIND is reading for the first time, the stats are: Java 90% cpu usage MySQL 10%
Very interesting. Profiling and performance optimization really are very important. I had some plans about implementing shortcut/tunneling to an RDBMS, but other assignments kept me from fulfilling them...
Do you have any patches for the things you mentioned above?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
