Clients need to be uniquely identified, then you can track and return content to them accordingly. So, you need some form of authentication / identification / authorization. Web2py has access control built in and this might provide all you need to get you started.
Regards On Wednesday, April 2, 2014 6:27:52 PM UTC+2, [email protected] wrote: > > I'm having a major issue with a web2py application in a production > environment. It is easily reproducible and causing major issues. > > At it's most basic level I can make a new function which does just one > thing - dumps something out to a log, appends to a file, posts an xmlrpc > response, etc. all results are the same. > > The result is If multiple clients request the same controller action at > the same time, only one of the requests is processed, and all clients > receive the same response. > > For example, 2 clients call "myfunction". Both get a response, but > "myfunction" writes to a log, file, or makes an external request only once! > This is a major issue, because many functions make an xmlrpc call to > another server, and everyone gets the same data, not what they requested. > > For what it is worth, these requests are coming in from Javascript/Ajax - > although that should not matter, multiple clients should be able to request > the same URL and get the correct data for what they posted. If these > requests are separated by 1 second, then they work normally, but any less > and this problem appears. > > Is there something missing here? A decorator or request._xxxx variable > that needs to be set? > > Any insight is greatly appreciated. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
