hiding behind auth doesn't get you protected by DDoS. opening a process inside a web2py app vs pure python depends on you comparing oranges to apples. web2py env with the default webserver is a threaded env, your pure python process probably isn't.
On Friday, November 18, 2016 at 8:34:46 AM UTC+1, Si An wrote: > > I'm asking why opening a process in a python script takes much less time > than opening the same python code/process in a web2py application. > > Also yes I will consider your second point but I think I will hide it > behind authentication > > On Thursday, 17 November 2016 22:53:50 UTC, Niphlod wrote: >> >> well... you're asking why opening a process in python rather than doing >> it directly takes more time. no wonders there: of course it takes more >> time! Especially if your process writes lots to stdout/stderr that python >> needs to collect. >> >> BTW: never ever ever run ANY external process from the webserver: you >> could easily be DDoSed AND you incur in lots of issues (random timeouts, >> memory issues, leaks, and aforementioned slowness). >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
