cr...@animalhead.com schrieb:
On Aug 27, 2009, at 10:43 AM, Bill Moseley wrote:
Use sprite sheets to reduce the number of required connections.
I looked up sprite sheets and they seem to be graphics that include
lots of little tiled figures used in video games.
How does a browser know to
Michael Ludwig wrote:
Sprites are useful for collections of related of the same size and
purpose.
You don't have to restrict them to images of the same size. You can use
a sprited image to replace any fixed size image, and any background
image that repeats in one direction or the other (but
Thanks for your comments. They lead to lots to think about and try.
I looked up sprite sheets and they seem to be graphics that
include lots of little tiled figures used in video games.
How does a browser know to split them up into separate images that
pages can then call out individually?
On Thu, Aug 27, 2009 at 5:20 PM, cr...@animalhead.com wrote:
Use a CDN and cache static content forever -- and rarely hit your serve.
In the end, each page view should only be one request to your mod_perl
server anyway.
My site uses all defined headers to encourage proxies and browsers to
Adam Prime schrieb:
Michael Ludwig wrote:
Sprites are useful for collections of related of the same size
and purpose.
You don't have to restrict them to images of the same size. You
can use a sprited image to replace any fixed size image, and any
background image that repeats in one
On Wed, Aug 26, 2009 at 9:23 PM, cr...@animalhead.com wrote:
I have no idea what EU::MM is. Candy from Europe?
Good guess, but it's actually ExtUtils::MakeMaker. It's the CPAN
install mechanism that Module::Build was written to replace.
My plan was to run the script the first time under
Perrin Harkins wrote:
It's not a run time option. The subject is a mod_perl2 script, that
can only be used within the Apache2 server. I can't conceive why the
DB name would ever change, and multiple programs won't use the module.
Some people have many apache installations on one machine, or
On Wed, Aug 26, 2009 at 3:43 AM, cr...@animalhead.com wrote:
The short story is that it's a mod_perl2 mechanism for optimizing
the KeepAlive option in the Apache2 server. The long story is at
http://www.animalhead.com/CloseKeepAlive.html
Interesting. But, is there really a probem to solve
On Aug 27, 2009, at 10:43 AM, Bill Moseley wrote:
On Wed, Aug 26, 2009 at 3:43 AM, cr...@animalhead.com wrote:
The short story is that it's a mod_perl2 mechanism for optimizing
the KeepAlive option in the Apache2 server. The long story is at
http://www.animalhead.com/CloseKeepAlive.html
On Thu, Aug 27, 2009 at 5:20 PM, cr...@animalhead.com wrote:
Yes that's the point, but I would substitute 'apache processes' for
'mod_perl processes'.
This is a mod_perl module, right?
My site's front page preloads sixty-some jpg thumbnails. Years ago it was
evident that KeepAlive On was
I'm working toward contributing a module with this working title
to CPAN, and would like your comments and advice.
The short story is that it's a mod_perl2 mechanism for optimizing
the KeepAlive option in the Apache2 server. The long story is at
http://www.animalhead.com/CloseKeepAlive.html
On Wed, Aug 26, 2009 at 6:43 AM, cr...@animalhead.com wrote:
I'm tentatively convinced it's worth contributing, but you're welcome
to tell me why it's not.
I think that setting a very short Keep-Alive timeout would be almost
as good. More importantly, you shouldn't serve any static files from
cr...@animalhead.com wrote:
I'm working toward contributing a module with this working title
to CPAN, and would like your comments and advice.
A non-code comment, but there seems to be some consternation about the
same terms as perl itself license. See the link below:
On Aug 26, 2009, at 7:03 AM, Perrin Harkins wrote:
What's GP Perl?
The general purpose Perl library is headed at /usr/local/lib/perl5
on my system. What I was asking is whether there's any reason
to put Apache2::CloseKeepAlive in it, being as it's so specialized,
or just copy it to a
On Wed, Aug 26, 2009 at 11:41 AM, cr...@animalhead.com wrote:
The general purpose Perl library is headed at /usr/local/lib/perl5
on my system. What I was asking is whether there's any reason
to put Apache2::CloseKeepAlive in it, being as it's so specialized,
or just copy it to a
On Aug 26, 2009, at 7:39 AM, Adam Prime wrote:
A non-code comment, but there seems to be some consternation about
the same terms as perl itself license. See the link below:
http://perlbuzz.com/2009/07/help-end-licensing-under-same-terms-as-
perl-itself.html
Inside many programmers,
On Aug 26, 2009, at 9:05 AM, Perrin Harkins wrote:
On Wed, Aug 26, 2009 at 11:41 AM, cr...@animalhead.com wrote:
The general purpose Perl library is headed at /usr/local/lib/perl5
on my system. What I was asking is whether there's any reason
to put Apache2::CloseKeepAlive in it, being as it's
On Wed, Aug 26, 2009 at 12:21 PM, cr...@animalhead.com wrote:
How does one specify that? It sounds like esoteric knowledge that
only a few users will know, and I'd like to empower people not to
clog up their GP Perl library with a module that can be used in
exactly one place.
It's in the
Including a note about how to do something in an installation dialog,
for people who wouldn't otherwise know, is not controlling anything.
If that's against CPAN principles, the principles need some work!
cmac
On Aug 26, 2009, at 9:30 AM, Perrin Harkins wrote:
On Wed, Aug 26, 2009 at 12:21
Seriously, this is not something you need to be concerned about.
There are dozens of places for people to get information about how to
install CPAN modules. Most people use the CPAN shell and set it up to
put things where they want them.
- Perrin
On Wed, Aug 26, 2009 at 1:31 PM,
cr...@animalhead.com wrote:
Including a note about how to do something in an installation dialog,
for people who wouldn't otherwise know, is not controlling anything.
Please don't put a dialog in your installation process! CPAN is supposed to be
automatic after it's been configured. There are
The installation process needs to know at least:
1. where the accompanying DB-building script should go
2. where the DB that the app builds should go
How can such necessary things be determined, other than by asking
the user?
I was just going to add a note before or after these two queries,
cr...@animalhead.com wrote:
The installation process needs to know at least:
1. where the accompanying DB-building script should go
Module::Build knows where to put bin/ or script/ files and it does so according
to how Perl and CPAN are configured. I assume EU::MM does too.
2. where the DB
On Aug 26, 2009, at 11:44 AM, Michael Peters wrote:
cr...@animalhead.com wrote:
The installation process needs to know at least:
1. where the accompanying DB-building script should go
Module::Build knows where to put bin/ or script/ files and it does
so according to how Perl and CPAN are
24 matches
Mail list logo
