Re: jcr2spi spi2dav Sending large data

[Angela Schreiber <an...@day.com>]

hi jozef

> Well I had to increase maximum heap size for both client and tomcat
> server in order to be able to send 20mb binary property, and it was
> damn slow. I think most of the problem was by this base64 conversion.

probably the easiest (least effort) solution would be
to have an alternative implementation for RepositoryService.addProperty
and RepositoryService.setValue in spi2dav.

an alternative to the global binary store (that consequently
would allow to keep the 'ValueProperty' (that sends the
value array in a webdavish xml-body) would be a straight
forward PUT for single-valued properties. that could (no garantuee)
already work on the server.
for multi-value properties a multipart request could be used.
but that would require some additions on the server.

can you open an issue for that?

regards
angela

Re: jcr2spi spi2dav Sending large data

[Jozef Wagner <jo...@gmail.com>]

Hi Angela,

Thank you for your response!

> > I would like to ask about the status of this issue.
> > Is there some plan/roadmap (no matter how vague)? How do you see it in
> > terms of time and resources?
>
> this issue doesn't have high priority for me.
> what i can offer you is:
>
> - quickly hack it in for non-multivalued properties.
> - leave multivalued props for the moment
> - add a patch to the issue (both for spi2dav and jcr-server)
>
> i definitely won't have the time to test it as it
> would be necessary. if you could do that, that would
> help a lot.
>
> would do you think?

That would be great. We don't have large multivalued properties and
our most common node would be of nt:file type.

We would of course test it, as we plan to use it after all :)

Best,
Jozef Wagner

Re: jcr2spi spi2dav Sending large data

[Angela Schreiber <an...@day.com>]

hi jozef

> I would like to ask about the status of this issue.
> Is there some plan/roadmap (no matter how vague)? How do you see it in
> terms of time and resources?

this issue doesn't have high priority for me.
what i can offer you is:

- quickly hack it in for non-multivalued properties.
- leave multivalued props for the moment
- add a patch to the issue (both for spi2dav and jcr-server)

i definitely won't have the time to test it as it
would be necessary. if you could do that, that would
help a lot.

would do you think?
angela

> Sorry if it seems I'm pressing on you, I'm not :). I just want to know
> it in order to be able plan things in my project.

Re: jcr2spi spi2dav Sending large data

[Jozef Wagner <jo...@gmail.com>]

Hi,

I would like to ask about the status of this issue.

Is there some plan/roadmap (no matter how vague)? How do you see it in
terms of time and resources?

Sorry if it seems I'm pressing on you, I'm not :). I just want to know
it in order to be able plan things in my project.

Thank you in advance,
Jozef Wagner

On 1/9/08, Jozef Wagner <jo...@gmail.com> wrote:
> Hi Angela,
>
> On 1/9/08, Angela Schreiber <an...@day.com> wrote:
> >
> > can you open an issue for that?
> >
>
> Done, http://issues.apache.org/jira/browse/JCR-1300
>
> Best,
> Jozef
>

Re: jcr2spi spi2dav Sending large data

[Jozef Wagner <jo...@gmail.com>]

Hi Angela,

On 1/9/08, Angela Schreiber <an...@day.com> wrote:
>
> can you open an issue for that?
>

Done, http://issues.apache.org/jira/browse/JCR-1300

Best,
Jozef