Closed willend closed 8 years ago
This part actually worked fine in the older setups (including the flask one in Munich) simply by starting multiple manage.py runworker .
(And seems to be the same here by trial and error - do you really think it is necessary to do clever thread-handling here?)
Technical University of Denmark
Department of Physics Neutrons and X-rays for Materials Physics Fysikvej
Building 307x-apple-data-detectors://1/0
DK-2800 Kongens Lyngbyx-apple-data-detectors://1/0
Direct +45 2125 4612tel:+45%202125%204612
Mobil +45 2125 4612tel:+45%202125%204612 Fax +45 4593 2399tel:+45%204593%202399
pkwi@fysik.dtu.dkmailto:pkwi@fysik.dtu.dk
Den 10/12/2015 kl. 00.08 skrev "Jakob Garde" notifications@github.com<mailto:notifications@github.com>:
Oooooh thread safety! No problem, we just need a few critical sections
— Reply to this email directly or view it on GitHubhttps://github.com/McStasMcXtrace/McWeb/issues/37#issuecomment-163431050.
we don't have actualy critical sections, but a much smaller likelyhood that a clash will happen. This is because the multithreading happens from an external process
Seems to work OK now, closing.
Oooooh thread safety! No problem, we just need a few critical sections