I grant you that the wording of my post sounds a little bit “odd,” but I did intend it that way.   My reasoning was, in part, to clearly convey that ... for the purposes of this project and thus of this immediate discussion, “to mod_perl or not to mod_perl, is not the question.”   It is, in fact, out-of-bounds.

Mind you, I don’t have any particular aversion to that method of web-site deployment.   With untold thousands of very-successful installations worldwide, the stability and general “good-ness” of that strategy is not in doubt.   I have used it and I would use it again.   But, for a multitude of reasons that do not have any bearing at all to “the good-ness (or not...) of mod_perl,” it’s going to be phased out for this project.   The code is going to become much more “deployment platform agnostic,” even to the point where it will no longer always be the case that Apache is even present.   Hence my attempts to carefully frame the question and to set boundaries of discussion around it.

I would love to find specific references to articles that talk about issues relating to the adaptation of the core logic of a web-application among different avenues of deployment.   (Hence my mention of mod:://Plack.)   Never mind why the choice was made, what the choice should be, or why a particular choice is right or wrong ...   what particular issues have The Monks run into when doing such a thing.   That’s my humble petition.

It would suit me just fine, and I think it would be equally relevant, if the discussion talked about “going the other way.”   References to web-sites outside of this one would be very helpful.   “Details, details.”

Now, back to counting bit-beads ... 00010101 ... 00010110 ...