Torbjörn Törnkvist

fyi: I had the same problem on my Mac. But by adding the UpdateHostKeys, as suggested + using ssh-add, the problem went away. (excellent tool btw :-) )

Well, Yaws could keep a X bytes buffer and flush it when it is "filled". I've been experimenting with our streaming REST application and e.g a 4k buffer gives a...

Yes, I'm using it already. It's no biggie to write your own buffering (as I already have done), but could perhaps be convenient if Yaws supported it out of the...

Ideally, it should not change the current API or adding something new. Just a config param 'StreamingBufferSize' which per default is Zero, i.e buffering is turned off, preserving the current...

No, I mean the yaws_api:stream_chunk_deliver/2 and friends... So, for example, when the user code, running in the Yaws process, returns control, it can do it by either: {streamcontent, MimeType, Data}...

Indeed! He needs to get up to speed again... ;-)

Just a little observation; I did a version where I used the stream_process* stuff to write directly on the socket. The result was a little bit slower than the "old"...

ok, perhaps a simple first approach could be to just open up yaws_api.erl to have a function for hard_setconf/2.

Sorry if I was unclear, but I meant the max allowed size of a header value. The reasoning behind this is to try and defend the system from malicious code...

Hm...we have done the transition to 80 columns already. I've pushed the code to my fork in a branch named: 80-columns So before any new changes are made you probably...