Perl-Uwe

• Website: www.perl-uwe.com/
• About: German Perl Hacker. I organise the Hamburg-PM meetings.

Recent Actions

• Posted Mojolicious workshop in Hamburg to Perl-Uwe

  The Hamburg perlmongers will be doing a Mojolicious workshop in Hamburg on Sathurday, 28th of January, 10:00 am.

  No prior knowledge is necessary, Marcos Rebelo will give an introduction. And later w…

• Commented on Downwards compatibility, and a surprising find
  Max, we use your modules. :)...
• Commented on Some nifty things you can do with Catalyst on Plack
  I'm interested in your middlewares. And thanks for the informative post. I especially like the static part....
• Commented on Photos from the SF.pm Perl-Critic talk
  Can you please post the slides? Thanks a lot....
• Commented on In Praise of NYTProf
  You can use Devel::Cover for that. (The HTML layout is taken from it.)...

Recent Actions from Perl-Uwe

Comment Threads

• Aristotle commented on Some nifty things you can do with Catalyst on Plack

  No.

  With Last-Modified and/or ETag, the browser will include the information you need to be able to send a 304 response with no entity body when asking for these resources again (which is good for periodically changing resources such as feeds).

  But with an Expires header in the far future, the browser won’t even ask again until that much time has passed. It reduces the per-page overhead for these resources from a tiny linear one to zero. It also helps client-side page load speed because the browser never needs to roun…

• Aristotle commented on Downwards compatibility, and a surprising find

  Another point: even if that query doesn’t work and you need the original form, you shouldn’t need such bulky transliterations:

  //*[translate(local-name(.), "BUTON", "buton")="button"
  or (translate(local-name(.), "INPUT", "input")="input" and @type="submit")]

  After all, it doesn’t matter whether you compare “ADDRESS” or “address” with “input”, it’s gonna fail either way.

• Ashley Pond V commented on Some nifty things you can do with Catalyst on Plack

  "the only reason to do it this way" - I think there might be another good reason. Take this example-

  /js/efa92b/file.js v /js/file.js?efa92b

  The first is ephemeral. The second is likely to continue to resolve to something sensible. End users may copy the first URI to find it broken later or even immediately. Robots may also continue to look for it and put pointless 404s in your logs for years because it got stashed in some dump file somewhere.

  So, your approach seems ideal. Please, please get any of your generalizable middlewares out to the CPAN. I'm sure many of us w…

• Ashley Pond V commented on Some nifty things you can do with Catalyst on Plack

  Whoops. Asked for your middlewares too soon. I mean late. I mean I see the ones discussed are on the CPAN already. What I get for jumping in a thread this late. Thanks!

• Aristotle commented on Some nifty things you can do with Catalyst on Plack

  Hmm, I meant to write an entry to mention that I had pushed them out to CPAN. It looks like I never got around to that at all. In any case, the code is out there. (Insert X-Files theme here.)

Responses to Comments from Perl-Uwe