get a path component in a
HTTP get request which is UTF-8 encoded and escaped. For example
http://ja.wikipedia.org/wiki/%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8
, which is a Japanese string if you decode it back to unicode. That
encoding works fine in two directions, and all
is UTF-8 encoded and escaped. For example
http://ja.wikipedia.org/wiki/%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8
, which is a Japanese string if you decode it back to unicode. That
encoding works fine in two directions, and all other properties used in
the http scheme such as query
not sure what you mean. On the wire you get a path component in a
HTTP get request which is UTF-8 encoded and escaped. For example
http://ja.wikipedia.org/wiki/%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8
, which is a Japanese string if you decode it back to unicode. That
encoding works
):
"""
CCUserSource is a ZPatterns plug-in intended to be used as a user source in
LoginManager. It queries a database adapter to acquire authentication
information on a user, and sets a user's role based on the user's age. A
database connection with an id of cc_user_database must be visible.
it can marshal and that
can't be changed without breaking the standard.
The alternative would be sending Python pickles encoded as
XML-RPC binary over the wire.
You could hack xmlrpclib to marshall those object, but I dont recommend
it. Those objects can be big (but lazily evaluated), and you
