pas-dev — Development mailing list.

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv16887/src/Org/Bgw/Pas

Modified Files:
	Response.pm 
Log Message:
added no warnings to buffer join

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv23694/src/Org/Bgw/Pas

Modified Files:
	RequestHandler.pm 
Log Message:
added content length to outbound header...

[Pas-dev] pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas
In directory sc8-pr-cvs1:/tmp/cvs-serv23694

Modified Files:
	ChangeLog 
Log Message:
added content length to outbound header...

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv9867/src/Org/Bgw/Pas

Modified Files:
	Page.pm 
Log Message:
added minor metrics tracking

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv8399/src/Org/Bgw/Pas

Modified Files:
	Page.pm 
Log Message:
added minor metrics tracking

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv4820/src/Org/Bgw/Pas

Modified Files:
	RequestHandler.pm 
Log Message:
added minor metrics tracking

[Pas-dev] pas/src/Org/Bgw/Pas/Psp CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas/Psp
In directory sc8-pr-cvs1:/tmp/cvs-serv10828/src/Org/Bgw/Pas/Psp

Modified Files:
	Compiler.pm 
Log Message:
added minor metrics tracking

[Pas-dev] pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas
In directory sc8-pr-cvs1:/tmp/cvs-serv10828

Modified Files:
	ChangeLog INSTALL 
Log Message:
added minor metrics tracking

[Pas-dev] pas/conf CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/conf
In directory sc8-pr-cvs1:/tmp/cvs-serv10828/conf

Modified Files:
	sample.pas.conf 
Log Message:
added minor metrics tracking

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv10828/src/Org/Bgw/Pas

Modified Files:
	Page.pm RequestHandler.pm 
Log Message:
added minor metrics tracking

[Pas-dev] pas CVS commit

[Jason S. <fa...@us...>]

Update of /cvsroot/pas/pas
In directory sc8-pr-cvs1:/tmp/cvs-serv14137

Modified Files:
	Makefile 
Log Message:

added a test target to invoke the unit test wrapper, tidied up a little formating.

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory sc8-pr-cvs1:/tmp/cvs-serv12506/src/Org/Bgw/Pas

Modified Files:
	Page.pm 
Log Message:
added query_string method...

[Pas-dev] pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas
In directory sc8-pr-cvs1:/tmp/cvs-serv12506

Modified Files:
	ChangeLog 
Log Message:
added query_string method...

[Pas-dev] proposal: PSP caching policy

[Kyle R . B. <mo...@vo...>]

This proposal is based on the earlier email about PSP optimziation and
caching.  This proposal explains the requirement for rendering policy.

The proposal is to add a new page directive called renderPolicy:

  <%@ page renderPolicy = "dynamic" %>
  <%@ page renderPolicy = "dynamic-params([query-param-list])" %>
  <%@ page renderPolicy = "dynamic-config([config-param-list])" %>
  <%@ page renderPolicy = "static" %>

The behavior of the directive is as follows:

dynamic: 
  This is the default, it is the same as PSP currently operates:
  PSP pages are 'run' to render the HTML output.  Included PSP's are 
  placed in the including PSP verbatim at compile time.

dynamic-params:
  The request handler uses the values of the given query/post paramers.  
  For each unique combination of the parameters, a cache file name is 
  computed. the PSP in quesiton is rendered and the result stored in 
  the cache file.  That cache file is served up at request time for PSP
  pages that are cached in this manner.  For included PSPs, the cached
  content is included into the enveloping dynamic page dynamicly by
  including the rendered cache file.

  For related approaches, see memoization and the Memoize CPAN module.

  Actualy this could be implemented in the request handler, but it might
  be better implemented as code that is injected into the compiled page
  by the PSP compler that does the dynamic checking.

dynamic-config:
  This works as dynamic-params, the only difference being that the
  dependency is on configuration file paramters instead of request-time
  parameters.

static:
  The PSP code is rendered and cached at compile time.  At request time
  the cached rendering is served.  For includes, the static cached 
  rendering is included into the enveloping dynamic page at compile time.


The complation should support multiple instances of: dynamic-params and
dynamic-config.  The specified parameter names should 'stack up' and be
unifieid, then the combined list used to determine which cache-file needs 
to be accessed.

The use of this directive will undoubtedly complicate the development 
and testing process while building sites with Pas, but it does allow 
for very fine-grained control of content rendering policy.  

The initial intention of this directive is to allow for control and 
optimization - page rendering times can be reduced by specifying 
caching policies in this manner.

A secondary implication of this is that developers can now virtualize
some of the page rendering and not worry about the performance 
implicaitons.  An example might be the choice of color schemes to
use in a cascading style sheet - mark the style sheet as 'static',
and have the color chocies be dynamic based on configuration file
paramters.  Then the .css file is rendered once, but you only need 1
.css file per configuration (say you're supporting mulitple websites 
on the same codebase) each with thier own branding.

An importiant issue here is that if we support multiple rounds of cache 
control inspection and staic-rendering during compliation of the main 
(or parent) PSP, then we can use this feature like a macro system.  A
PSP could be marked as 'static', and generate PSP code that will be run
at request time (this could be arbitrarily nested, which is something
we need to both support and watch out for).   The idea here is to write
the static PSP in a very abstracted or refactored manner and have it
generate the code that needs to be run at request time.  This can be
viewed similarly to the macro systems supported LISP or Scheme.

The second implication of this feature is potentialy the most powerful
for allowing site developers higher and higher levels of abstraction
for developing their websites.



Commentary and rebuttal is encouraged.

Kyle


-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

[Pas-dev] pas/src/Org/Bgw CVS commit

[Jason S. <fa...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw
In directory sc8-pr-cvs1:/tmp/cvs-serv15112/src/Org/Bgw

Modified Files:
	ConfigTest.pm 
Log Message:
Added tests for absolute and relative pathed include directives in the 
pas.conf file.

Added 2 test.conf files for use in later unit tests.

[Pas-dev] pas/conf CVS commit

[Jason S. <fa...@us...>]

Update of /cvsroot/pas/pas/conf
In directory sc8-pr-cvs1:/tmp/cvs-serv15112/conf

Added Files:
	test.include.conf test.pas.conf 
Log Message:
Added tests for absolute and relative pathed include directives in the 
pas.conf file.

Added 2 test.conf files for use in later unit tests.

[Pas-dev] fixing relatively included config files.

[Mental P. <me...@ne...>]

Hey, doing this didnt work:
include ../customproduct/conf/common.conf

I modified Config.pm. When you're trying to include a file, it does this
now:
   if($line =3D~ m|^\s*include\s+(\S+)\s*$|) {
      my $file =3D $1;
      if (! -f $file){
        $file =3D $ENV{PAS_BASE}.$file;
        if (! -f $file){
          die "Error including $file no file found.\n";
        }
      }
      $self->config_files($self->config_files(),$file);
      unshift(@lines,$self->getFileAsLines($file));
      next;
    }

Are we interested in having this commited? It should probably be
refactored a little, but it fixes my problem of relative include
directives.....=20



--=20
Mental Patient <me...@ne...>

[Pas-dev] pas/src/Org/Bgw/Base CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Base
In directory sc8-pr-cvs1:/tmp/cvs-serv7820/src/Org/Bgw/Base

Modified Files:
	Common.pm 
Log Message:
quieted warnings for makeGetSetMethods under mod_perl

[Pas-dev] pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas
In directory sc8-pr-cvs1:/tmp/cvs-serv7820

Modified Files:
	ChangeLog 
Log Message:
quieted warnings for makeGetSetMethods under mod_perl

[Pas-dev] random thought

[Kyle R . B. <mo...@vo...>]

Response time.  Rendering time.  Something that could be done, largely
automaticly, by Pas (at least when turned on by an administrator) is to
gather usage statictics on a per-PSP file, or per-Page object URI basis.
Using these stats, the statistics could then be used by Pas to make 
recommendations to administraotrs or developers on pages that would be
better off as either static content, or at least cached.

The level of caching can be thought (in large part) as a continuium from
a static page (either .html or stored in a caching proxy), to a .psp, or
included .psp, who's renderd output is cached by pas for serving, or in the
case of an include, re-inclusion into larger pages.  

For dynamic-need pages, it is possible to imagine Pas caching the output
of a highly dynamic (peraps a section is dependant on the user's login 
information, or organization, or cookie) temporarily on the file system,
in a LRU (least recently used) style cache for easy inclusion into other
pages.  So if there is a very commonly renderd and used page fragment, Pas
could render it, store it with the parameters that uniquely identify it
(like the user's user id for instance, or an organization ID, or an MD5
hash of the components in a shopping basket [!]) and just use the chached
version when servicing requests.

Perhaps these caching approaches would be controlable by a developer and/or
an administrator - a pragma at the top of the .psp which specifies some
kind of caching (or dynamic need) policy?  Settings in the configuration
file?

Those types of statistical metrics could also be used and post-processed
to provide system level profiling of whole and partial page render times.  
That kind of data is be invaluable to developers whishing to cut down on
response times and make their site faster.


Kyle




-- 

------------------------------------------------------------------------------
Wisdom and Compassion are inseparable.
        -- Christmas Humphreys
mo...@vo...                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

[Pas-dev] Pre-install check

[Mental <Me...@Ne...>]

Yo. I think I made a list of all the modules pas needs. Do we want/need a
pre-install check script you can run that reports missing modules?

The INSTALL file is a little out of date, and an automated check-install
script might be nice.=20


--
Mental (Me...@Ne...)

                    let it rain a day, a week, a year
                   let it rain a thousand years a day
             that's the divine answer to all the shed tears
          that's the cyclic flood well known by those who know

--Samael "Rain"

CARPE NOCTEM, QUAM MINIMUM CREDULA POSTERO.

GPG public key: http://www.neverlight.com/pas/Mental.asc

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory usw-pr-cvs1:/tmp/cvs-serv30478/src/Org/Bgw/Pas

Modified Files:
	RequestHandler.pm Response.pm 
Log Message:
added methods so you can add arbitrary http headers

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory usw-pr-cvs1:/tmp/cvs-serv18835/src/Org/Bgw/Pas

Modified Files:
	RequestHandler.pm Response.pm 
Log Message:
added methods so you can add arbitrary http headers

[Pas-dev] pas/src/Org/Bgw/Pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas/src/Org/Bgw/Pas
In directory usw-pr-cvs1:/tmp/cvs-serv10752/src/Org/Bgw/Pas

Modified Files:
	RequestHandler.pm Response.pm 
Log Message:
added methods so you can add arbitrary http headers

[Pas-dev] pas CVS commit

[Kyle R. B. <mo...@us...>]

Update of /cvsroot/pas/pas
In directory usw-pr-cvs1:/tmp/cvs-serv10752

Modified Files:
	ChangeLog 
Log Message:
added methods so you can add arbitrary http headers