Hi All,
Have there been any more developments off-list about the format of the
config file for WSGI deployment?
I'd like to apply the entry points labeling idea to sections in the
pipeline config file and propose the following extensions to the format.
Here is an example to start with:
[datab
At 05:23 PM 8/7/2005 +0100, James Gardner wrote:
>This has three advantages:
>
>1. Standardisation between similar WSGI middleware components becomes
>easier because we could all agree to name standard database connection
>parameters as database so middleware can be more interoperable.
>Non-stan
Phillip J. Eby wrote:
> This approach is capable of doing everything you've proposed, except
> that it doesn't provide access to the private configuration data of
> individual services. It would be possible, however, to load the
> service chain from a deployment file without instantiating
> a
At 07:33 PM 8/7/2005 +0100, James Gardner wrote:
>Phillip J. Eby wrote:
>
>>This approach is capable of doing everything you've proposed, except that
>>it doesn't provide access to the private configuration data of individual
>>services. It would be possible, however, to load the service chain f
