2008/9/30 Frank Wiles <[EMAIL PROTECTED]>:
> On Mon, 29 Sep 2008 22:16:12 +0200
> André Warnier <[EMAIL PROTECTED]> wrote:
>
>> We have also looked at various data organisations over time.
>> Regarding storing large objects directly in a database, the one issue
>> is always that (because of the obj
On Tue, 30 Sep 2008, Cosimo Streppone wrote:
In data 30 settembre 2008 alle ore 00:09:52, James Smith <[EMAIL PROTECTED]>
ha scritto:
On Mon, 29 Sep 2008, Cosimo Streppone wrote:
In data 29 settembre 2008 alle ore 23:45:05, James Smith
<[EMAIL PROTECTED]> ha scritto:
There are good reas
In data 30 settembre 2008 alle ore 00:09:52, James Smith
<[EMAIL PROTECTED]> ha scritto:
On Mon, 29 Sep 2008, Cosimo Streppone wrote:
In data 29 settembre 2008 alle ore 23:45:05, James Smith
<[EMAIL PROTECTED]> ha scritto:
There are good reasons to store images (especially small ones) in
On Mon, 29 Sep 2008, Cosimo Streppone wrote:
In data 29 settembre 2008 alle ore 23:45:05, James Smith <[EMAIL PROTECTED]>
ha scritto:
There are good reasons to store images (especially small ones) in databases
(and with careful management of headers in your mod_perl).
Some of you have mis
James Smith wrote:
There are good reasons to store images (especially small ones) in
databases (and with careful management of headers in your mod_perl).
Some of you have missed inherent problems with the file systems
even balanced heirarchical tree - ones in a shared server
environment whic
In data 29 settembre 2008 alle ore 23:45:05, James Smith
<[EMAIL PROTECTED]> ha scritto:
There are good reasons to store images (especially small ones) in
databases (and with careful management of headers in your mod_perl).
Some of you have missed inherent problems with the file systems
eve
There are good reasons to store images (especially small ones) in
databases (and with careful management of headers in your mod_perl).
Some of you have missed inherent problems with the file systems
even balanced heirarchical tree - ones in a shared server
environment which can lead to gross
In data 29 settembre 2008 alle ore 21:00:41, Mark Stosberg
<[EMAIL PROTECTED]> ha scritto:
This question isn't so much a mod_perl question, as it is a question
about building high performance websites with Perl.
We have a large, busy, database application that relates to millions of
photos, w
On Mon, Sep 29, 2008 at 3:00 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote:
> We have a large, busy, database application that relates to millions of
> photos, which we also need to store and display.
Have you read Cal Henderson's book about how Flickr works? It's a bit
extreme, but interesting. A
On Mon, 29 Sep 2008 22:16:12 +0200
André Warnier <[EMAIL PROTECTED]> wrote:
> We have also looked at various data organisations over time.
> Regarding storing large objects directly in a database, the one issue
> is always that (because of the object sizes), it makes any operation
> on the rows of
On Mon, 29 Sep 2008 15:00:41 -0400
Mark Stosberg <[EMAIL PROTECTED]> wrote:
> This question isn't so much a mod_perl question, as it is a question
> about building high performance websites with Perl.
>
> We have a large, busy, database application that relates to millions
> of photos, which we
I'm pretty sure that the consensus is to never actually store the files in
the database. What actual inconsistencies are you seeing that you are
trying to fix?
On Mon, Sep 29, 2008 at 1:00 PM, Mark Stosberg <[EMAIL PROTECTED]> wrote:
>
> This question isn't so much a mod_perl question, as it is
On Mon, Sep 29, 2008 at 3:16 PM, André Warnier <[EMAIL PROTECTED]> wrote:
> Oh, and I've thought of another advantage, in an Apache/web context : to
> send the content of a file to a browser, you can take advantage of the
> sendfile() call, which is very efficient. Now if your file is a blob in a
Mark Stosberg wrote:
This question isn't so much a mod_perl question, as it is a question
about building high performance websites with Perl.
We have a large, busy, database application that relates to millions of
photos, which we also need to store and display. We've been keeping the
meta dat
This question isn't so much a mod_perl question, as it is a question
about building high performance websites with Perl.
We have a large, busy, database application that relates to millions of
photos, which we also need to store and display. We've been keeping the
meta data about the photos in P
15 matches
Mail list logo
