Hello Graham, thanks for the response.
In other words, the only reason that the old style and deprecated API was > used was because was still supporting Apache 1.3. In mod_wsgi 4.0 don't > have that limitation can do it right without needing two different > implementations. > You mean in mod_wsgi 4.0 (which is the current trunk I guess) a rewrite of Input_read is possible. So no usage of ap_*_client_block is needed anymore, instead use the bucket brigade API directly ? Then in daemon mode the registration of the HTTP_IN input_filter is obsolete too ? I like this approach, because it makes it possible to share the code for Input_read in daemon and embedded mode. Do you think such an improvement will make it to mod_wsgi-4.0 ? What is the timeline for 4.0 ? For the long run mod_wsgi 4.0 will definitely work for us. Right know we are working with mod_wsgi-3.3, here I tried to work on a mod_dechunk myself and it seems to work. https://github.com/stephan-hof/mod_dechunk, still a prototype regarding error checking, logging and parametrization but already functional. Final version must come in the next two weeks. I know its not a good approach if requests go big, but for our application this is not expected. Regards, Stephan -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To view this discussion on the web visit https://groups.google.com/d/msg/modwsgi/-/wRYshQ7wZWMJ. 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.
