[Zope3-checkins] SVN: Zope3/trunk/doc/CHANGES.txt selling the new
publisher registry as new feature
Andreas Jung
andreas at andreas-jung.com
Mon Oct 31 15:04:15 EST 2005
Log message for revision 39783:
selling the new publisher registry as new feature
Changed:
U Zope3/trunk/doc/CHANGES.txt
-=-
Modified: Zope3/trunk/doc/CHANGES.txt
===================================================================
--- Zope3/trunk/doc/CHANGES.txt 2005-10-31 19:36:58 UTC (rev 39782)
+++ Zope3/trunk/doc/CHANGES.txt 2005-10-31 20:04:14 UTC (rev 39783)
@@ -114,6 +114,15 @@
be used by the client for API discovering, through three
methods: listAllMethods, methodHelp and methodSignature
+ - The publisher machinery is now completely pluggable. Publishers can be
+ registered and configured through ZCML (using the new 'publisher' ZCML
+ directive. see zope/app/publication/configure.zcml). Publishers are
+ registered for a sequence of request methods and a configurable list
+ of mimetypes. To register multiple publishers for the same request
+ method and the same mimetype (e.g. POST+text/xml: SOAP, XMLRPC)
+ publishers can be prioritized and publishers can introspect the request
+ environment to decide if they can handle a request or not.
+
Restructuring
- Mutable MessageIDs have been deprecated and will be removed in
@@ -137,14 +146,6 @@
See zope/i18nmessageid/messages.txt for more information.
- - The publisher machinery is now completely pluggable. Publishers can be
- registered and configured through ZCML (using the new 'publisher' ZCML
- directive. see zope/app/publication/configure.zcml). Publishers are
- registered for a sequence of request methods and a configurable list
- of mimetypes. To register multiple publishers for the same request
- method and the same mimetype (e.g. POST+text/xml: SOAP, XMLRPC)
- publishers can be prioritized and publishers can introspect the request
- environment to decide if they can handle a request or not.
Bug Fixes
More information about the Zope3-Checkins
mailing list