On Wed, Apr 16, 2008 at 12:00 PM, David Giragosian
<[EMAIL PROTECTED]> wrote:
>
> On 4/16/08, tedd <[EMAIL PROTECTED]> wrote:
> >
> > At 10:53 AM -0400 4/16/08, Andrew Ballard wrote:
> >
> > > On Wed, Apr 16, 2008 at 9:59 AM, tedd <[EMAIL PROTECTED]> wrote:
> > >
> > > > I saw one the other
On 4/16/08, tedd <[EMAIL PROTECTED]> wrote:
>
> At 10:53 AM -0400 4/16/08, Andrew Ballard wrote:
>
> > On Wed, Apr 16, 2008 at 9:59 AM, tedd <[EMAIL PROTECTED]> wrote:
> >
> > > I saw one the other day that caught my eye -- will look into it.
> >
> > >
> > > The first problem I see implementing t
On Wed, Apr 16, 2008 at 11:42 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
> Daniel Brown wrote:
>
> I guess it's a matter of preference - I tend to think that a shared
> hosting user is best restricted to whatever changes he can do
> in .htaccess (with php_admin_flag etc.).
I allow overrides
At 10:53 AM -0400 4/16/08, Andrew Ballard wrote:
On Wed, Apr 16, 2008 at 9:59 AM, tedd <[EMAIL PROTECTED]> wrote:
> I saw one the other day that caught my eye -- will look into it.
The first problem I see implementing the approach is the JavaScript
sandbox. JavaScript is allowed to read the
Daniel Brown wrote:
> On Wed, Apr 16, 2008 at 10:36 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
>>
>> I'm curious - why? To me php.ini seems to be exactly the kind of
>> thing you wouldn't the user to fiddle with - in a shared
>> environment.
>
> To allow flexibility for the user, and give
On Wed, Apr 16, 2008 at 10:36 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
>
> I'm curious - why? To me php.ini seems to be exactly the kind of thing
> you wouldn't the user to fiddle with - in a shared environment.
To allow flexibility for the user, and give them the opportunity
to customize
On Wed, Apr 16, 2008 at 9:59 AM, tedd <[EMAIL PROTECTED]> wrote:
>
> At 9:41 AM -0400 4/16/08, Andrew Ballard wrote:
>
> > On Wed, Apr 16, 2008 at 7:56 AM, tedd <[EMAIL PROTECTED]> wrote:
> >
> > > At 6:48 PM +0900 4/16/08, Dave M G wrote:
> > >
> > > > PHP list,
> > > >
> > > > I have a PHP sc
Daniel Brown wrote:
> On Wed, Apr 16, 2008 at 9:57 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
>> Daniel Brown wrote:
>> >
>> > And on a shared host, the likelihood of increased billing for
>> > overuse of memory.
>>
>> Except a shared hoster would probably not permit anyone to change
>> ph
On Wed, Apr 16, 2008 at 9:57 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
> Daniel Brown wrote:
> >
> > And on a shared host, the likelihood of increased billing for
> > overuse of memory.
>
> Except a shared hoster would probably not permit anyone to change
> php.ini :-)
I do. A lot of
At 9:41 AM -0400 4/16/08, Andrew Ballard wrote:
On Wed, Apr 16, 2008 at 7:56 AM, tedd <[EMAIL PROTECTED]> wrote:
At 6:48 PM +0900 4/16/08, Dave M G wrote:
> PHP list,
>
> I have a PHP script that resizes an image. It takes just about whatever
size and shrinks and crops it down to 320X240.
Daniel Brown wrote:
> On Wed, Apr 16, 2008 at 6:07 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
>>
>> > Actually, I have no idea what the potential dangers are.
>>
>> Using up all available memory is the only real "risk". It might
>> lead to swapping which in turn will most likely increase respon
On Wed, Apr 16, 2008 at 7:56 AM, tedd <[EMAIL PROTECTED]> wrote:
> At 6:48 PM +0900 4/16/08, Dave M G wrote:
>
> > PHP list,
> >
> > I have a PHP script that resizes an image. It takes just about whatever
> size and shrinks and crops it down to 320X240.
> >
> > I've found that these days, it's not
On Wed, Apr 16, 2008 at 6:07 AM, Per Jessen <[EMAIL PROTECTED]> wrote:
>
> > Actually, I have no idea what the potential dangers are.
>
> Using up all available memory is the only real "risk". It might lead to
> swapping which in turn will most likely increase response times.
And on a shar
On Wed, Apr 16, 2008 at 7:56 AM, tedd <[EMAIL PROTECTED]> wrote:
> At 6:48 PM +0900 4/16/08, Dave M G wrote:
>
> > PHP list,
> >
> > I have a PHP script that resizes an image. It takes just about whatever
> size and shrinks and crops it down to 320X240.
> >
> > I've found that these days, it's not
On Wed, Apr 16, 2008 at 5:48 AM, Dave M G <[EMAIL PROTECTED]> wrote:
> PHP list,
>
> I have a PHP script that resizes an image. It takes just about whatever
> size and shrinks and crops it down to 320X240.
>
[snip!]
>
> So sometimes I've seen an error in my logs that says:
>
> Fatal error: Allow
At 6:48 PM +0900 4/16/08, Dave M G wrote:
PHP list,
I have a PHP script that resizes an image. It takes just about
whatever size and shrinks and crops it down to 320X240.
I've found that these days, it's not uncommon for people to take
images straight off their digital camera, which can be 3
Dave M G wrote:
> I contacted my web host provider, and they recommended increasing the
> allowed allocation limit in "/etc/php.ini".
>
> Right now my allocation limit, assuming I'm looking at the right
> setting is 8 megabytes:
>
> memory_limit = 8M ; Maximum amount of memory a script may
PHP list,
I have a PHP script that resizes an image. It takes just about whatever
size and shrinks and crops it down to 320X240.
I've found that these days, it's not uncommon for people to take images
straight off their digital camera, which can be 3000X2000 pixels in
image size, even if the
18 matches
Mail list logo
