Re: Windows binaries 64bit for PHP [message #177997] |
Thu, 10 May 2012 12:02 |
Jerry Stuckle
Messages: 2598 Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 5/10/2012 2:49 AM, Michael Fesser wrote:
> .oO(Jerry Stuckle)
>
>> Repeatedly resizing the files is a huge waste of processor resources.
>
> Maybe you should get a decent machine? And "when needed" is not the same
> as "repeatedly". It's done _once_ and may only be repeated if someone
> would clear the image cache.
>
> Micha
>
Yup. And a cache is by definition temporary - meaning that the images
will have to be resized repeatedly.
Or are you going to create a 1TB image cache?
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
Re: Windows binaries 64bit for PHP [message #178021 is a reply to message #177997] |
Thu, 10 May 2012 19:09 |
Michael Fesser
Messages: 215 Registered: September 2010
Karma: 0
|
Senior Member |
|
|
.oO(Jerry Stuckle)
> Yup. And a cache is by definition temporary
This could mean minutes, but also years.
> meaning that the images
> will have to be resized repeatedly.
Only if someone intentionally deletes the cache.
> Or are you going to create a 1TB image cache?
If necessary, why not? Google caches almost its entire index of
websites.
But if you're so picky about definitions, don't call it an image cache,
but "automated creation of static image resources".
Micha
--
http://mfesser.de/blickwinkel
|
|
|
Re: Windows binaries 64bit for PHP [message #178024 is a reply to message #178021] |
Thu, 10 May 2012 19:32 |
Jerry Stuckle
Messages: 2598 Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 5/10/2012 3:09 PM, Michael Fesser wrote:
> .oO(Jerry Stuckle)
>
>> Yup. And a cache is by definition temporary
>
> This could mean minutes, but also years.
>
Yup, if you only get 200 hits a day it could be years. Active systems
typically measure this in minutes at best.
>> meaning that the images
>> will have to be resized repeatedly.
>
> Only if someone intentionally deletes the cache.
>
Or the image is deleted from the cache to make more room, which is
typically in seconds.
>> Or are you going to create a 1TB image cache?
>
> If necessary, why not? Google caches almost its entire index of
> websites.
>
Oh, so now you're writing systems as complicated as Google? ROFLMAO!
> But if you're so picky about definitions, don't call it an image cache,
> but "automated creation of static image resources".
>
> Micha
>
I'm using the term like it is defined. Just because you want to call a
cow a horse doesn't make it a horse.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|