On Wednesday, September 11, 2013 5:44:00 PM UTC+2, ajith c t wrote: > > sorry I am not executing the code in the load balancer. Let me say once > more, so it will be clear. > > I dont have any web2py code in the load balancer. > > What I meant is I have my code in another server(say X) , to which the > user is redirected by the load balancer(say Y). > > when I execute the webpy application from server X , the index function , > where my scheduler.queue_task call comes,in the default.py controller will > not be called as I cant access it from X. That is expected. So what I asked > was , for breaking down purpose shouldn't I move that call into the > scheduler.py file in the models folder as the model file will be called. > > I really don't get this part. Every controller in web2py gets executed as long as the request comes to the server. If you can reach a page and in your controller for that page you use queue_task(), you should definitely be able to enqueue a task. queue_task() is NOT meant to be used in models, because you'd queue a task for EACH and EVERY request coming in.
> > And I will use the "seperation of duties" approach. but can you just > confirm that the commands are correct. > > web part: python web2py.py -a yourpassword -p 8000 -i 0.0.0.0 scheduler python web2py.py -K appname let me stress it out once more: serving a web app in production with the included webserver is not going to provide stellar performances, although it definitely works. -- 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/groups/opt_out.
