Because ScriptRunner uses FastCGI, its performance should be close to embedded language solutions like mod_perl, but with a lot less worries about security and overflows. With ScriptRunner you can introduce all of your friends to Pike without forcing them to suffer bad performance or the (more likely) attachment to Apache. In addition, ScriptRunner does a lot of the unpleasant work of parsing incoming requests, allowing you to get right to the task of writing your code.

Right now, it's pretty early on in its development, so there are a lot of niceties present in Roxen or Caudium that aren't available, and it's not terribly well tested, so it could have some nasty bugs. Enough raw functionality is available to be highly useful; hopefully there will be interest in improving things in this area. ScriptRunner contains code written by others over the years; this is really more of a gathering of snippets into something more readily useful to others.

Requirements:

- Pike 7.6+ (available from http://pike.ida.liu.se)

• libfastcgi (available from http://www.fastcgi.com)
• Public.Web.FastCGI (available from http://www.siriushosting.com/pike/fastcgi.html)

  Features:

• Multi-threaded request handling
• Persistent interpreter
• Compiled object caching
• Incoming requests are parsed and passed to you in a request id object.
• Handles FCGI processing for you. Just return a string or control mapping from your parse() method.
• Preliminary Pike Server Pages support, which allows you to mix HTML and Pike in the same page.
• Tested to work with mod_fastcgi and mod_actions on Apache 1.3+

  Download:

  - http://hww3.riverweb.com/dist/scriptrunner/scriptrunner-0.2.tar.gz

• CVS browsing and snapshot downloads at http://buoy.riverweb.com:8080/viewrep/cvs/scriptrunner

  Installation:

  Apache users: see the file INSTALL.Apache in the source distribution for information on configuring Apache support for FastCGI.

  IMPORTANT: you must edit the first line of the ScriptRunner.fcgi application to include the complete path to the ScriptRunner installation directory:

  #!/usr/local/bin/pike -M/full/path/to/scriptrunner

  Make sure that you have satisified the prerequisites before continuing.

  Install and configure FastCGI support for your webserver so that *.fcgi files are treated as FastCGI applications.

  Simply copy the scriptrunner files to a FastCGI enabled web server (it's

Edit the scriptrunner application to specify an optional log file

(recommended).

Add a redirect to convert all requests to (*.pike) to /path/to/scriptrunner.fcgi($1) (actual syntax will vary based on the redirector you're using.

For example, if I've installed ScriptRunner so that the ScriptRunner.fcgi is called by the following request:

www.mysite.com/path/to/ScriptRunner.fcgi

and I put a pike script in /some/other/path.pike on my website, I need my redirect to internally change

www.mysite.com/some/other/path.pike

to

www.mysite.com/path/to/ScriptRunner.fcgi/some/other/path.pike

This is a common technique used by PHP and other languages. Alternately, you could use mod_actions to do the same thing:

   AddHandler scriptrunner-pike-script .pike
   AddHandler scriptrunner-pike-script .psp
   Action scriptrunner-pike-script /path/to/ScriptRunner.fcgi

In the long run, this may be a simpler option.

What does a script look like?

Pike scripts look a lot like C or Java, but the first thing you'll notice is that they're far less verbose. One of the nice things about Pike is that a lot of powerful language constructs and methods are available to you out of the box. For example, the following script will render the contents of the form variable "input" as text on a PNG image:

mapping parse(object id)
{
  // note that all of the most commonly used pieces of the request are
  // assembled in the request id object. 
  if(!id->variables->input)
    id->variables->input = "Default Text";
   // the last argument is set to 1 to ensure we get a font back, even
   // if we don't have the one we're looking for.
  object fnt = Image.Fonts.load_font("Times New Roman", 72, 0, 1);
  object img = fnt->write(id->variables->input);
  string output = Image.PNG.encode(img);
  return (["data": output, "type": "image/png"]);
}

The following example demonstrates Pike's database-independent SQL API. In this example, we're running a database query and returning the results as a table. Also note that we've added some code to speed processing: we keep the database connection open between requests.

object sql;
string sql_url = "mysql://user:pass@localhost/mydb";
string parse(object id)
{
  if(!sql)
    sql = connect_sql(sql_url);
  // note that we use 'sprintf' like features here. the replacement variables
  // get automatically quoted as appropriate for the underlying database.
  // we're also using the 'simple query' interface that returns the result
  // as an array of mappings (hashes)
  array sql_result = sql->query("SELECT firstname, lastname, phone FROM addresses WHERE lastname like %s", "Smith%");
  if(!sizeof(sql_result))
    return "sorry, there were no entries.";
  String.Buffer r = String.Buffer();
  // In addition to standard object oriented method calls, 
  // Pike supports operator overloading, which allows objects to
  // appear as though they were simple datatypes. This allows us to
  // start with strings, and very simply replace the more efficient
  // string buffer object, with only 2 changes to our code
  r += "<table>";
  // let's loop through the result set
  foreach(sql_result; int index; mapping row)
    r += sprintf("<tr><td>%s, %s</td><td>%s</td></tr>", 
                 row->lastname, row->firstname, row->phone);
  r+="</table>";
  // we could have just as easily cast the buffer to a string.
  return r->get();
}
object connect_sql(string url)
{
  object s;
  if(catch(s = Sql.Sql(url)))
    throw(Error.Generic("Unable to connect to the database.&#110;"));
  return s;
}

Some example scripts (they all start with test) are included to give you a head start. More extensive documentation is available in the source distribution.

Support

Pike ScriptRunner is free software made available under the GPL/LGPL/MPL licenses. We're just getting started, so we're not totally organized yet. For the time being, send email to the Pike mailing list: pike at roxen dot com or to the author: bill at gotpike dot org.

Powered by PikeWiki2