From: Christian Decker on
Hi all,

I want to create a service where people can upload their images and
later on access them. I'm using Hibernate for the meta data such as
image title, comments and relationships with other Domain-Entities in
my system, but I have absolutely no clue about how to best store the
images. Storing them in the database would obviously be a complete
overkill, while storing them directly on the disk does have some
drawbacks as I wanted to serve the images along with the other static
content from a different host for caching and speed reasons.
Any idea on how to do this? Maybe a Content Repository like JackRabbit
would be fit for the job?

Regards,
Chris
From: Arne Vajhøj on
Christian Decker wrote:
> I want to create a service where people can upload their images and
> later on access them. I'm using Hibernate for the meta data such as
> image title, comments and relationships with other Domain-Entities in
> my system, but I have absolutely no clue about how to best store the
> images. Storing them in the database would obviously be a complete
> overkill, while storing them directly on the disk does have some
> drawbacks as I wanted to serve the images along with the other static
> content from a different host for caching and speed reasons.
> Any idea on how to do this? Maybe a Content Repository like JackRabbit
> would be fit for the job?

If you have some database power and the pictures are not totally
huge, then I will recommend the database solution. Much easier
to manage.

Arne
From: Lew on
Arne Vajhøj wrote:
> Christian Decker wrote:
>> I want to create a service where people can upload their images and
>> later on access them. I'm using Hibernate for the meta data such as
>> image title, comments and relationships with other Domain-Entities in
>> my system, but I have absolutely no clue about how to best store the
>> images. Storing them in the database would obviously be a complete
>> overkill, while storing them directly on the disk does have some
>> drawbacks as I wanted to serve the images along with the other static
>> content from a different host for caching and speed reasons.
>> Any idea on how to do this? Maybe a Content Repository like JackRabbit
>> would be fit for the job?
>
> If you have some database power and the pictures are not totally
> huge, then I will recommend the database solution. Much easier
> to manage.

Yeah, there is absolutely nothing "obvious" about a database being "overkill".

--
Lew