Stefan L�tzkendorf schrieb:
Oliver Zeigermann wrote:
Folks!
For quite some time I have thought about something like a store that directly takes copy/move/delete which is currently done by the Macro implementation that does a single request per resource to the stores. However, there may be many stores which could make sense of the direct combined calls, for example the file store.
What would be needed for this would be a check if such a macro operations concernes a single store only. If yes and this particular store supports the MacroStore interface it should be dispatched to it. If not the old code should be executed.
What about binding here?
With binding move or copy should be simple, because only the (parent) bindings have to be changed. The resource with its UURI should not be touched. (I wonder who this works currently)
I see. Does MacroImpl already take care of this?
How do I find out which stores are involved? Analysing what has been configured in Domain.xml?
what about that? Uri source, destination; if (source.getStore() == destination.getStore()) { // source and destination are in the same store }
Glad I asked someone ;) My solution would have been crazy...
Other problems? Comments?
What about transactions and file stores? With the simple file store I can imagine that it can direcly map such MacroStore methods to file system calls but with the tx file store?
Tx file store would need core additions, but they should be doable. Just something like the marker for deleted files there should be something for *folders* to be copied/moved/deleted. At commit time the operation is simply done on a file level with a fast relink if there was a move, etc.
Oliver
Oliver
Stefan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
