On Dec 17, 2007 8:22 AM, Christian Zagrodnick <[EMAIL PROTECTED]> wrote:
> There are different kinds of request (BrowserRequest, XMLRPCRequest,
> FTPRequest, …) which depend on the "channel" or server zope is accessed
> through.

We have this use case:

The server is accessed through a number of different channels, each
associated with some URL re-writing.  This includes in most cases a
++skin++<name> path element, often with additional path elements.  The
skin used is associated with the channel.

We have a couple of different cases where there are XML-RPC methdods
that should be associated with the channel as well.  Using anything
other than ++skin++ seems like silliness in this case: we need
something that can associate the request with a channel, regardless of
the type of the request (XML-RPC, browser, etc.).

We don't care that ++skin++ is the name of the request-typing path
element, but we do want a single path element that can mark the
request regardless of the request type.  Preferably without
re-architecting our applications.


Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to