Thanks Niphlod. I realize this solution was probably using the response.js in a manner for which it wasn't intended.
I took the idea from http://stackoverflow.com/questions/20633959/ajax-response-in-web2py I guess that's not the right approach - or perhaps I deviated from the idea. Is there a better approach which lets you have two ajax components, one for the form and one for the results? If not I can redesign it like I did previously and make the form a non-ajax component. On Tuesday, November 18, 2014 6:35:10 AM UTC-5, Niphlod wrote: > > response.js creates a header. I can only assume that pythonanywhere impose > a limit on the length of the header. What you're doing is wrong on many > levels for http specs. > -- 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.
