Comments for A Foolish Manifesto

Comment on The Rise and Fall of mod_perl by Florian Ragwitz

Florian Ragwitz — Tue, 09 Mar 2010 02:34:49 +0000

I’m glad to see you resolved your issues.

I understand the that Engine::HTTP::Prefork doesn’t work on Win32. However, we also got an Engine::Plack, and Plack itself has a variety of server backends, like Stardust, Twiggy, which are probably less unix specific than Prefork and could have a better chance of running on Windows, without having to use Catalyst’s development-only server.

Comment on mod_perl: For Your Health! by The Rise and Fall of mod_perl

The Rise and Fall of mod_perl — Tue, 09 Mar 2010 01:28:48 +0000

[...] from ActiveState) to run certain scripts persistently. I did some research and discovered that using mod_perl in win32 was feasible and you can indeed turn it on for parts of your site. Yet again, all was well with the [...]

Comment on New DBIx::Class::Journal by Shlomi Fish

Shlomi Fish — Sun, 21 Feb 2010 13:03:32 +0000

All tests passed on Mandriva Linux Cooker. Thanks for your work.

Comment on Do Passwords Right by fREW Schmidt

fREW Schmidt — Thu, 04 Feb 2010 18:47:23 +0000

@Andrew: I thought I made it clear that this scheme does use a unique salt per user. Sorry I wasn’t clear enough for you

@Michael: indeed.

Comment on Do Passwords Right by Michael Peters

Michael Peters — Thu, 04 Feb 2010 14:38:13 +0000

Salts are only kept secret if they aren’t unique per-password. If you have a unique salt it’s typically stored as part of the hashed password, so that the encrypted password can be used as the salt when checking a login attempt to make sure they hash to the same thing.

Comment on Paranoid Deletion in DBIx::Class by Darren Duncan

Darren Duncan — Thu, 04 Feb 2010 09:04:55 +0000

If you’re going to be paranoid about deletes, you need to be paranoid about updates too, as updates can easily be just as destructive. Hence change auditing records are good.

Comment on Do Passwords Right by Andrew Rodland

Andrew Rodland — Thu, 04 Feb 2010 07:28:38 +0000

Not “you can have a unique salt per password”. You *must* have a unique salt per password, chosen randomly when the password is set or reset, or none of the other stuff is even worth the time you spent on it.

Fortunately your example *does* get it right, so there isn’t any additional work to be done!

Comment on An Exposition on Specific Time Saving Code by fREW Schmidt

fREW Schmidt — Fri, 29 Jan 2010 18:34:25 +0000

@nperez: the main reason we haven’t gone that route is that our grids are certainly not homogeneous. I briefly considered doing what you are talking about, but I just am not convinced that we would have the flexibility that we need. The same goes for DBIC::API.

Comment on An Exposition on Specific Time Saving Code by nperez

nperez — Fri, 29 Jan 2010 16:47:05 +0000

That’s interesting that you do a lot of the code gen inside Perl. For our platform, we use TT instead fo spit out the the record format, columns definitions, etc for the data store and grid. Mostly, I end up passing a result source directly via the stash to the template, and it is only a simple matter at that point of iterating the columns.

DBIx::Class has an underdocumented “feature” that you can put pretty much whatever you want into the add_column statement, so I attach a small “hint” hash that contains things like whether it should be displayed in the grid, its display order, etc. This lets me very easily “bleed” implementations from the DB up to the display layer.

In the end, our datastores and grids are restful and we have them talking to DBIC::API. All of the setup to get to that point is just an index method to spit out the initial page.

I had toyed with at one point going even further and disconnecting the UI completely from TT and have it query the backend for its config (you can attach metaData to your results and it will reconfigure the record fields automagically), but time constraints left me with the TT approach to convey the structure.

Comment on Template.Tiny by Adam Kennedy

Adam Kennedy — Tue, 26 Jan 2010 23:39:16 +0000

Your other alternative here is Jemplate, which is Ingy’s more accurate clone of Template::Toolkit.