Hi, I only drop in here every now and then. It may be worthwhile to mention that I never got the WSGi support fully working under Jython. I played with it under Geronimo and Tomcat. The mechanism used here is WSGI.
The issue is not with Jython but with the way servlets handle POST data. The aforementioned containers actually completely gobble up the POST-data (which is available to the servlet in an (java) inputStream, parse it into parameters, meaning the POST-data cannot be send forward to the WSGI adapter for parsing in Django. I've also had similiar issues with file-uploads, the issue being there blocking and non-blocking I/O. Since I stumbled upon this discussion about WSGI .... DISCLAIMER: It may have been a faulty configuration of mine, but I don't think it was, it may have been a problem for which there is allready a solution ... I don't know, and I don't think so. Just wanted to share this ... I didn't investigate further, I did find a very nasty workaround that actually suited my needs better than actually fixing it. ________________________________ From: Russell Keith-Magee <freakboy3...@gmail.com> To: django-developers@googlegroups.com Sent: Tue, 5 January, 2010 0:44:57 Subject: Re: WSGI support in Django On Mon, Jan 4, 2010 at 11:46 PM, Gustavo Narea <gustavona...@2degreesnetwork.com> wrote: > Hi, > > One more update about the WSGI related improvements for Django: > > I have created a Mercurial branch to keep track of these changes and > keep them synchronized with trunk: > http://bitbucket.org/Gustavo/django-wsgi/ > > Even though I know it's late for 1.2 at this point, please keep in mind > that part of these enhancements were supposed to be a high priority for > the 1.2 release [1] (GSoC-2). This branch implements more features than > the official http-wsgi-improvements branch and is complete/working. And > again, I am willing to help you with anything you need to get it merged, > such as writing docs and discussing the implementation further. There's a very important reason why the feature list is called 'High Priority" and not "Must Have". We're all volunteers, so it's impossible for us to know exactly how much time we will have to dedicate to Django. Therefore, our goals need to be (and are) expressed in terms of relative priorities, rather than in terms of absolutes. Malcolm was the champion behind GSOC-2; unfortunately, Malcolm has been buried under real-life and work stuff, so he hasn't been able to shepherd the GSOC-2 changes into trunk. This is unfortunate, but there isn't much we can do about this. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
