On Sun, 07 Sep 2008 08:09:15 +0100 Amanda Waite <Amanda.Waite at Sun.COM> wrote:
> Hi there, > > I'd like to propose an integration into OpenSolaris of the FastCGI > Application Libraries (from hereon referred to as "FastCGI"). Strong +1 in principle. I hadn't even realised these were separate from mod_fcgid as already packaged (OK, I wasn't looking)! > I've > attached a first draft of the Arc Case for discussion. This > integration will deliver 32-bit and 64-bit libraries along with > 32-bit and 64-bit versions of the cg-fcgi executable (see questions > below). There are no difficult issues with this integration that I > can see currently and it's built fine in my workspace. The > documentation is unbundled and that includes man pages for the > cgi-fcgi executable and for a couple of library calls. I'm not sure > if these are covered by the license under which the source code > bundle is released. Other libraries seem to have a main man page, > pcre(3) for example, do I need to write one of these? if so does it > need to describe the API in detail or can it just tell users where it > is and what's available? Other outstanding questions that I have are: > > - Do I include static libraries? I've deliberately removed them in > the draft Arc Case > - There's been no development for 5 years. How do we provide ongoing > support? It's a very stable interface: CGI and mod_fastcgi haven't moved either (though the latter could be because mod_fcgid more-or-less obsoleted mod_fastcgi). > - Is it really necessary to include 32-bit and 64-bit versions of the > executable? Is there any reason not to? > There also doesn't appear to be any bundled tests which is a bit of a > problem. Interesting. Do you have anything in mind as a basis for a test kit? I'm just wondering whether it might be worth revisiting cg-eye and building a few tests on top of it. As regards documentation, I'm bothered about the lack of it in many of our packages. I'd suggest that any solution beyond a pointer to the website should be part of an across-the-board effort rather than a one-off. But a brief README "what these are, where to find more info" should be in order. -- Nick Kew
