|
List Info Thread: Re: Initializing a Tool with config variables?
[1]
|
||||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||||
Re: Initializing a Tool with config variables? |
|
List Info Thread: Re: Initializing a Tool with config variables?
[1]
|
||||||||||||
|
about | contact Other archives ( Real Estate discussion Medical topics ) |
||||||||||||
![](http://www.cherrypy.org/wiki/CherryPySpec<img
src='http://www.archivesat.com/images/blushing.gif'>http://w
ww.cherrypy.org/wiki/CherryPySpec:</a>
"The request.config dict SHOULD also contain _cp_config
entries from
handler
methods and their containers (such as controller classes)
and merge
those
values into request.config. However, since the very nature
of different
dispatchers is to enable different controller architectures,
the
decision
of where to attach and collect _cp_config entries is
dispatcher-specific.
Also, dispatchers SHOULD allow app.config entries to
override _cp_config
entries; this allows deployers to more easily override
developer
defaults."
And a snippet from "help(cherrypy._cpconfig)":
Architecture
------------
CherryPy Requests are part of an Application, which runs
in a global
context,
and configuration data may apply to any of those three
scopes:
Global: configuration entries which apply everywhere
are stored
in
cherrypy.config.
Application: entries which apply to each mounted
application are
stored
on the Application object itself, as 'app.config'.
This is a
two-level
dict where each key is a path, or "relative
URL" (for example,
"/" or
"/path/to/my/page"), and each value is a
config dict. Usually,
this
data is provided in the call to tree.mount(root(),
config=conf),
although you may also use app.merge(conf).
Request: each Request object possesses a single
'Request.config'
dict.
Early in the request process, this dict is populated
by merging
global
config entries, Application entries (whose path
equals or is a
parent
of Request.path_info), and any config acquired while
looking up
the
page handler (see next).
Declaration
-----------
Configuration data may be supplied as a Python
dictionary, as a
filename,
or as an open file object. When you supply a filename or
file,
CherryPy
uses Python's builtin ConfigParser; you declare
Application config
by
writing each path as a section header:
[/path/to/my/page]
request.stream = True
To declare global configuration entries, place them in a
[global]
section.
You may also declare config entries directly on the
classes and
methods
(page handlers) that make up your CherryPy application
via the
'_cp_config'
attribute. For example:
class Demo:
_cp_config = {'tools.gzip.on': True}
def index(self):
return "Hello world"
index.exposed = True
index._cp_config = {'request.show_tracebacks':
False}
Note, however, that this behavior is only guaranteed for
the default
dispatcher. Other dispatchers may have different
restrictions on
where
you can attach _cp_config attributes.
Robert Brewer
System Architect
Amor Ministries
fumanchu<img src=)
googlegroups.com
To unsubscribe from this group, send email to
cherrypy-users-unsubscribe