James, So very true. I tell you what, I've been meaning to contribute something to the project because it is a very nice framework but at this point I have a week to do this and getting code into trunk takes longer than a week. With cherrypy I can just write a Tool that filters the request before it's parsed, that's easier than managing branches, given my timeline. Once I'm done I'll give the code to the django people to do with it whatever they'd like.
Also streaming uploaded data to disk isn't just important to my application it's essential to the frameworks stability. RAM used to buffer files is RAM that can't be used for concurrent requests and on improperly configured servers... well you get the point. I can't believe anybody let's users upload anything using django, it's begging to be DDoS'd. I've not seen RAM buffering for file uploads in almost 6 years until Django and Rails hit the scene. Sends chills up my spine. Vance On Jan 14, 2008 10:56 AM, James Bennett <[EMAIL PROTECTED]> wrote: > > On Jan 14, 2008 12:01 PM, Vance Dubberly <[EMAIL PROTECTED]> wrote: > > Kind of a bummer, guess I'll be using cherrypy for this project. Was > > hoping to use django but it looks like there is no way to hook into > > the request response loop before the request is parsed. :( > > If streaming uploads are vital to your application, you might consider > pitching in to help with supporting them in Django. > > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." > > > > > -- To pretend, I actually do the thing: I have therefore only pretended to pretend. - Jacques Derrida --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
