Revision 1207

Jump to revision:
Author:	pje
Date:	Thu Jun 26 00:38:05 2003 UTC (20 years, 10 months ago)

Log Message:

'peak.web' is born; just interface sketches and a draft of 'BaseInteraction'
for now.  CGI support has been moved from 'peak.running.zpublish' into
'peak.running.commands' (for "raw" CGI/FastCGI) and 'peak.web' (for the
PEAK high-level publishing framework).  You can use 'peak CGI someName' to
adapt 'someName' to a 'running.IRerunnableCGI' and run it as a CGI/FastCGI.
This will form the basis for creating the web version of an app later;
you'll do something like::

   class MyAppAsCGI(web.CGIPublisher):
       app = binding.New(MyAppClass)

And then use 'peak CGI import:somepkg.MyAppAsCGI' to run it.  Or, if your
app wants to exec a config file, you might define your CGIPublisher
subclass as an adapter from MyAppClass to IRerunnableCGI, rather than
invoking it directly.

Changed paths:

Path	Action	Text Changes	Prop Changes	Diff to Previous
PEAK/CHANGES.txt	modified	X		(diff to previous)
PEAK/setup.py	modified	X		(diff to previous)
PEAK/src/peak/peak.ini	modified	X		(diff to previous)
PEAK/src/peak/running/commands.py	modified	X		(diff to previous)
PEAK/src/peak/running/interfaces.py	modified	X		(diff to previous)
PEAK/src/peak/running/zpublish.py	deleted
PEAK/src/peak/web	added
PEAK/src/peak/web/__init__.py	added	X	X
PEAK/src/peak/web/interfaces.py	added	X	X
PEAK/src/peak/web/publish.py	added	X	X