[Libwebsockets] browser flow-control

Per Bothner per at bothner.com
Sun Mar 12 21:30:45 CET 2017

On 03/12/2017 01:18 PM, Andy Green wrote:

>> But what if the file is infinite? I.e. it's printing in an endless
>> loop?
>> I could tolerate this too, as long as the user can type ctrl-C, and
>> that
>> is handled and gets sent to the looping process, and kills that
>> process.
>> But the ctrl-C isn't getting through - I'm not sure why, but I suspect
>> it's just a scheduler in the browser that isn't designed to handle
>> these situations.
> This is true in both, eg, ffox and chrome?

Yes.  Chrome is better, in that an infinite-looping DomTerm display doesn't freeze
the entire browser - just the DomTerm tab/window.  But each window is still only
going to be one process, as JavaScript itself is single-threaded.
	--Per Bothner
per at bothner.com   http://per.bothner.com/

More information about the Libwebsockets mailing list