For various reasons, mod_wsgi development has been stuck in a deep dark hole for a number of years. In general that hasn't mattered as the last version was very stable and so bugs simply weren't arising.
All the same, there has been a very slow dribble of minor improvements such as this which have been requested but haven't been done. The hopefully good news is that am getting very close now to pulling mod_wsgi from that deep dark hole and giving it a rebirth. I don't want to say too much about it right now but shouldn't be too long now before I can. I have added this issue into a fresh list of new work which would be targeted once development is resurrected. This is not on the existing Google Code site where mod_wsgi is currently held. The Google Code site will be deprecated with everything there being moved off as things start up again. Only important issues from the bug tracker there will be moved across so can start over and not instantly feel overwhelmed and fall back into the hole. Graham On 01/05/2014, at 3:33 AM, Eran Rom <[email protected]> wrote: > I was wondering if there are any news on the subject. Browsing the bug list I > did could not identify any related bug (but it may be my apache/wsgi > ignorance). > Does it make sense to open a bug? Were there any additional requests for > having mod_wsgi in daemon mode working with chunked transfer encoding. > As a previous poster my use case is also getting Openstack Swift working with > Apache and mod_wsgi. > > Thanks very much! > Eran > > On Wednesday, March 6, 2013 12:00:05 PM UTC+2, Stephan Hofmockel wrote: > Hi David, > > I don't know if keeping all data of a single request in memory is an option > for you. For us it is acceptable and we are running this on many servers in > production. > https://github.com/stephan-hof/mod_dechunk > > Regards, > Stephan > > Am Montag, 4. März 2013 13:04:26 UTC+1 schrieb [email protected]: > Hi Graham, > > In continuation to this thread, I am working on getting Openstack Swift to > work with Apache and mod_wsgi and using daemon mode. The luck of support for > Transfer-Encoding chunked seem be one of the last pieces of the puzzle. > > I get it that it did not make it into 4.0 - is there a 4.1 planned? Does it > seem to be high enough in the priority? > > Thanks > David > > > > > Do you think such an improvement will make it to mod_wsgi-4.0 ? > > I have been wanting to do it for a long time. > > > What is the timeline for 4.0 ? > > Don't know. Things dragging on so long that have back ported a lot of > stuff so can bring out 3.4 instead. Usually I wouldn't put new > features in a minor release but will this time. > > Graham > > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
