Yes I use sqlite as the default web2py database backend. The record is created at the end of the transfer, why should have been a lock during the transfer ? This "lock" does not occur without Cherokee/uWSGI, why ?
To check this, what is the simplest controller code to achieve an upload (without database) ? 2011/1/4 mdipierro <[email protected]>: > Do you use sqlite? That may be locking. > > > On Jan 3, 5:49 pm, PhE <[email protected]> wrote: >> Following Massimo's advice on my previous post on file upload with >> rocket/ssl, I decided to give another try to cherokee/web2py. >> >> Now I've got reliable ssl file uploads : 4 successful uploads of a 5 >> MB file (3 to 4 minutes transfer each). >> This is a great forward step ;-) >> >> But I still have a big issue : during the transfer the web2py service >> is unavailable. >> An attempt to access the index page of web2py makes Cherokee to >> respond : >> 503 Service Unavailable >> Cherokee web server 1.0.15 (Ubuntu), Port 443 >> >> I tried to access the page from a different browser to avoid session >> locking with same error. >> >> Note that I use a dummy application with only one table, one upload >> field and no code at all ! (I use the really fresh 1.91.6) >> Upload is done by admin pagehttps://mysite/myapp/appadmin/insert/db/mytable >> >> I used uWSGI following this recipe >> :http://web2pyslices.com/main/slices/take_slice/110 >
