And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Not all of these packages have been tested.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
There were no changes to 1.10pre4.
The changes since 1.10pre3 are:
* ResponseMixin redirect() renamed to send_redirect().
The changes since 1.10pre2 are:
* Request classes now have a get_path_info() method.
* Redirect now sends the session id cookie when it is defined. The
logic has been moved into ResponseMixin.redirect().
* SessionBase now has a session_vars() method that returns a list of
the names in the session.
* Random page URI handling is back to 1.10pre1 state. The base_path
used to split the requested URI will always end with '/'.
* Random page URI cracking has been moved into the get_page_from_uri()
method. This allows application to redefine the cracking method.
* More documentation updates - especially in the prepackaged classes
chapter.
* Most samples have been changed to allow them to be run using the
al-httpd program.
Albatross is a small and flexible toolkit for developing highly stateful web
applications. The toolkit provides the following:
* Browser based sessions via automatically generated hidden form fields
(cryptographically signed to ensure integrity).
* Server side sessions via a session server or file based session store.
* Powerful and extensible templating system which promotes separation of
presentation and implementation for improved program maintainability.
* Pagination of sequences and tree browsing are handled implicitly in the
templating system.
* Macros allow repeated HTML and special effects HTML to be defined in one
location.
* Lookup tables translate internal program values to arbitrary template code.
* Applications can be deployed as either CGI programs or as mod_python module
with minor changes to program mainline. Custom deployment can be achieved
by developing your own Request class.
* Highly modular application framework which is flexible and extensible which
allows many different application construction models. Eight Application
classes are provided while many more are possible.
* Comprehensive documentation including many installable samples.
A primary design goal of Albatross is that it be small and easy to use and
extend. Most of the toolkit is constructed from a collection of mixin classes.
You are encouraged to look at the code and to think of new ways to combine the
Albatross mixin classes with your own classes.
