Fork of WebGUI 7.10, maintained by Oqapi https://git.oqapi.nl/oqapi/webgui
Find a file
Doug Bell 8bd28e101f update Copy to work with ProgressBar and streaming
ProgressBar needs to handle streaming itself. When it does, all
AssetHelpers that use ProgressBar will need to remove their own
streaming handlers and just use ProgressBar's
2010-08-04 12:07:55 -05:00
docs Merge branch 'master' into WebGUI8, up to 7.9.10. Some tests failing due to changes in default content. 2010-07-27 22:55:57 -07:00
eg Add a missing newline. 2010-06-24 08:43:12 -07:00
etc missing admin in conf, fixed color on starter 2010-08-03 13:48:35 -05:00
lib update Copy to work with ProgressBar and streaming 2010-08-04 12:07:55 -05:00
sbin fix merge problems 2010-07-12 15:52:38 -05:00
share add new progressbar template 2010-08-04 11:57:56 -05:00
t Merge branch 'master' into WebGUI8, up to 7.9.10. Some tests failing due to changes in default content. 2010-07-27 22:55:57 -07:00
www remove bad background image 2010-08-03 13:58:43 -05:00
.gitignore
.perltidyrc
.proverc adding proverc file 2010-06-13 06:15:34 -05:00
app.psgi don't preload for development, and encode output as UTF-8 2010-05-10 17:02:09 -05:00
asset_status.ods Add a sheet to track Roles. 2010-03-05 15:17:05 -08:00
benchmark.pl Logging fallback 2010-04-13 17:46:43 -04:00
README some documentation additions/fixes 2010-05-10 17:00:48 -05:00
TODO Minor improvements 2010-04-18 14:51:24 -04:00
WebGUI-Session-Plack.pm Added WebGUI::Requestion/Response 2010-04-06 19:35:06 -04:00

This is the PSGI branch of WebGUI8

To try this out:

 1) Run testEnvironment.pl to install Plack
 2) $ cd <WebGUI directory>
 3) $ plackup app.psgi

Currently, the best performance is achieved via:

 plackup -E none -s Starman --workers 10 --disable-keepalive

You can benchmark your server via:

 ab -t 3 -c 10 -k http://dev.localhost.localdomain:5000/ | grep Req

I'm currently getting 370 requests/second, whereas I'm getting 430/second on the non-PSGI WebGUI8 branch.

= ARCHITECTURE =

* The root level app.psgi file loads all the config files found and
  loads the site specific psgi file for each, linking them to the
  proper host names.
* The site psgi file uses the WEBGUI_CONFIG environment variable to find the config.
* It instantiates the $wg WebGUI object (one per app).
* $wg creates and stores the WebGUI::Config (one per app)
* $wg creates the $app PSGI app code ref (one per app)
* WebGUI::Middleware::Session is wrapped around $app at the outer-most layer so that it can open and
  close the $session WebGUI::Session. Any other wG middleware that needs $session should go in between
  it and $app ($session created one per request)
* $session creates the $request WebGUI::Session::Request and $response WebGUI::Session::Response
  objects (one per request)