Yeah like Niphlod said, I wouldn't worry about web2py at all in that 
instance. web2py will not be the bottleneck, getting data from that other 
server will. So just cache the hell out of the calls to make as little 
requests as possible, load the stuff you need the communication for using 
ajax so the rest of the page can show while you get it to make it seem 
faster, etc.

-- 
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.

Reply via email to