Streaming the output or not does not make much difference here, because your source code is designed to read ALL input first. That causes the response feeling slow. Not to mention this approach won't work at all when dealing with large content.
A better way is to read a small amount of data and then relay it to the output. This is real streaming. Regards, Ray On Tuesday, August 19, 2014 1:16:02 AM UTC-7, Niphlod wrote: > > not really, except that it's not streamed. > > On Tuesday, August 19, 2014 10:12:55 AM UTC+2, Manuele wrote: >> >> Il 19/08/14 09:27, Niphlod ha scritto: >> > from cStringIO import StringIO >> > def whateveryoumaycall(): >> > content = fetch_the_resource() >> > f = StringIO() >> > f.write(content) >> > f.seek(0) >> > #set the correct headers, such as >> > response.headers['Content-Type'] = 'blablabla' >> > response.headers['Content-Length'] = 31298312098312 >> > ..... >> > return response.stream(content, ....) >> ok more or less is what I'm doing... is there any advcantage by >> returning response.stream(content, ....) instead of returning text as >> I'm doing now? >> >> Thanks >> >> M. >> > -- 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.
