Steve Vinoski
Steve Vinoski
This was apparently done in the very first version of the `yaws_rpc` module; see 1791e3dc. My understanding is that the module was originally written to support Haxe, so perhaps it...
Right, the backward compatibility issue is the problem with changing this.
Have you tried using the [Yaws streaming features](http://yaws.hyber.org/stream.yaws), specifically the non-chunked delivery approaches described on that page? Seems like that feature would give you complete control over your app's buffering.
Adding some sort of optional buffering helper/utility for non-chunked streaming could be useful. I guess it would be a server process that would serve as the streaming pid, providing an...
Just so I'm clear, you're suggesting that the `yaws_api:stream_process_deliver*` functions learn to respect a stream buffer size configuration setting?
OK, thanks @etnt. Now, don't you think @klacke should implement this, since he's now apparently returned from his world tour? :-)
Nice, @klacke ! I don't think it'll be too hard if we take the config variable route. The only hard part I can think of is how to test it?
I think that's OK, but I'll need to look into the issue more.
Yes, thanks, already working on it. Unfortunately this issue did not show up in the 23.0 release candidates, only in the 23.0 final release. We've had the `warnings_as_errors` setting for...
I just removed `warnings_as_errors` from `rebar.config` in 48686bbf.