#2070: Large streaming uploads
----------------------------------------+-----------------------------------
   Reporter:  [EMAIL PROTECTED]  |                Owner:  jacob         
     Status:  assigned                  |            Component:  Core framework
    Version:  SVN                       |           Resolution:                
   Keywords:  streaming, upload, large  |                Stage:  Accepted      
  Has_patch:  1                         |           Needs_docs:  0             
Needs_tests:  0                         |   Needs_better_patch:  1             
----------------------------------------+-----------------------------------
Comment (by Michael Axiak <[EMAIL PROTECTED]>):

 Replying to [comment:137 anonymous]:
 > I have tested multiple upload at the same time (difference browser
 instance). If there are more than two upload request, when a first request
 > is sent, it work properly. If I make a new call, an old stop immediately
 and a new one not create a session and temp file anymore.
 >
 > Django is great in advance, please keep it simple and work in common
 task.
 
 Hi,
 
 I have tested it with simultaneous file uploads and it worked fine. Could
 you please include more details? For instance, I don't think there would
 be any chance it would work in the development server. It may break in
 some FastCGI configurations, too. (The reason being that accepting
 multiple file uploads requires some multithreadedness.)
 
 -Mike

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2070#comment:138>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to