On Fri, Feb 12, 2010 at 6:01 AM, Graham Dumpleton <
[email protected]> wrote:

> If you really want to go down that path, happy to try and get that C
> extension module together for you, but with apswigpy you could at
> least test concept first.
>

That's really good of you to offer. But you mean making this extension
module as a sort of minimal subset of apswigpy, using the same approach,
right? So it too would only work in embedded mode? I'll gladly try out
apswigpy and tell you how it goes, but in the end I will probably want to
avoid changing over to embedded mode if at all possible.

The only way around that would be for mod_wsgi to provide a special
> feature whereby you could provide a response header which specifies
> the user and mod_wsgi picks that up in main Apache server processes,
> whether embedded or daemon mode used and makes update transparently.
>

This actually sounds quite neat and minimal — if it's an obviously
non-conflicting header like X-modwsgi-trans-request-user that gets removed
on the Apache side so it only exists over the daemon process divide, and
only exists when specifically configured, that would be a fairly safe and
low-effort feature to add, right? And works in either embedded or daemon
mode.

Are there more cases besides the authenticated username, of information that
people might commonly want to pass back to Apache? I'm wondering if this is
a special case or whether a general scheme like 'X-modwsgi-trans-%s' for
string-valued key-value pairs is warranted.

Because users wanted me to stick with mod_wsgi really only being about
> WSGI. I did think about making it part of mod_wsgi. But then I would
> have still had to maintain it even though no one was using it.
>

Fully understood. Would this apply also to the transient-header-passing
approach above? I.e. is it too out-of-scope to be included, and thus should
be a separate module? I imagine (unfoundedly) that it would be a fairly
commonly-desired feature though.

Thanks,

- Gulli

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to