Thomas Mueller wrote:
Hi,
a possible way improve this would be to make usage of
the global data store (JCR-926)
That would be a solution. The idea is to avoid temporary copies of the
data, and persist large objects as early as possible. I'm not sure if
the data store should be used in the Jackrabbit SPI client
the data store would be on the server. but i would introduce
means to be able have the binary QValue only 'contain' the
uri (or some other sort of identifier) and maybe the length.
the uri would be resolved only if the stream is obtained from
the value... something like that.
and basically the object could be sent to the server upon
creating the initial qvalue already... what would be needed
was a separate qvaluefactory implementation and some extensions
to the jackrabbit-webapp that would allow to read/write the binary
objects irrespective of their jcr property.
that's what i meant my making usage of the global data store.
angela
