From 39fccbbfbceacaf1b3d5fb6f03a07fbe4d861969 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 6 Aug 2008 03:30:40 +0000 Subject: - Small url dispatch overhaul: the ``connect`` method of the ``urldispatch.RoutesMapper`` object now accepts a keyword parameter named ``context_factory``. If this parameter is supplied, it must be a callable which returns an instance. This instance is used as the context for the request when a route is matched. - The registration of a RoutesModelTraverser no longer needs to be performed by the application; it's in the bfg ZCML now. --- CHANGES.txt | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index a76a91bc0..eac0c6b48 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,14 +1,27 @@ -After 0.2.6 +0.2.7 - Add a ``request_type`` attribute to the available attributes of a ``bfg:view`` configure.zcml element. This attribute will have a value which is a dotted Python path, pointing at an interface. If the request object implements this interface when the view lookup - is performed, the appropriate view will be called. + is performed, the appropriate view will be called. This is meant + to allow for simple "skinning" of sites based on request type. An + event subscriber should attach the interface to the request on + ingress to support skins. - Remove "template only" views. These were just confusing and were never documented. + - Small url dispatch overhaul: the ``connect`` method of the + ``urldispatch.RoutesMapper`` object now accepts a keyword + parameter named ``context_factory``. If this parameter is + supplied, it must be a callable which returns an instance. This + instance is used as the context for the request when a route is + matched. + + - The registration of a RoutesModelTraverser no longer needs to be + performed by the application; it's in the bfg ZCML now. + 0.2.6 - Add event sends for INewRequest and INewResponse. See the -- cgit v1.2.3