Re: Reading only RGB portion of an image, file_get_conents minus file headers etc
| From: | Alex Nikitin | Date: | Tue, 24 Jan 2012 02:43:28 +0000 |
| Subject: | Re: Reading only RGB portion of an image, file_get_conents minus file headers etc | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-316386@lists.php.net to get a copy of this message | ||
Absolutely agreed. A part of what i was asking deals with what he is
actually doing...
--
The trouble with programmers is that you can never tell what a
programmer is doing until it’s too late. ~Seymour Cray
On Mon, Jan 23, 2012 at 9:37 PM, Robert Cummings <robert@interjinn.com> wrote:
> On 12-01-23 09:29 PM, Alex Nikitin wrote:
>>
>> Have you done image processing? In my experience, with image
>> generation, photography and processing, typically you are bound by
>> resources when processing large amount of files than your connection,
>> or sometimes even disk io.
>
>
> It really depends on what you're doing with images, if it's intensive
> processing that's already implemented in the gd or imagick library to which
> you can just punt, then how much overhead do you think PHP is really going
> to add since these are C implemented libraries? Sure, if you are
> manipulating pixels one by one within your PHP code you may be running into
> resource issues, but for scaling images, or cropping, or even clipping and
> overlaying... you're not usually doing a whole lot within PHP itself. The
> love is happening in the C code in these cases. This is why when working
> with these libs you get a resource handle and not a string. The resource
> handle almost certainly maps to a native GD or imagick structure.
>
>
> Cheers,
> Rob.
> --
> E-Mail Disclaimer: Information contained in this message and any
> attached documents is considered confidential and legally protected.
> This message is intended solely for the addressee(s). Disclosure,
> copying, and distribution are prohibited unless authorized.