Hi Michael, others, On Tue, 9 Aug 2022 at 20:28, Michael Merickel <mmeri...@gmail.com> wrote:
> This harkens back to the discouraged write() callable in WSGI PEP 3333 > returned by the start_response() invocation. The PEP as well as Pyramid as > a framework would encourage you to map the logic into an app_iter as Bert > suggested. > > I think you'll want to define a file-like object that you can write to and > set as the app_iter. The question will be whether you try to do this by > writing from a separate thread or in some other way because once you return > control to the WSGI server to iterate on your app_iter then you are no > longer in control - you'll need some buffer between where you're generating > your parquet file and what you're returning from the app_iter. I don't > think a simple tempfile is good enough because you want the app_iter to > wait instead of stopping when it hits an EOF unless you know that you've > reached the end of the buffer. > > Thank you for the good commentary. This is very good insight, I didn't think about the threading issue. I think I will attempt an approach where I just use a buffer like Theron mentioned and then have a library to write from the buffer from another thread. Br, Mikko -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAK8RCUvKj%3DUAeESmWmauVnhBzSObH3jhKeori7GwOJkKkvaPKA%40mail.gmail.com.
