Reply to thread

Message

<blockquote data-quote="Starwer" data-source="post: 1111285" data-attributes="member: 149636">Hi Ashley,&nbsp;You surely have a point. What probably happens is that the key-repeat is faster than the blast-command, leading to a traffic jam of the communication. the keystroke events fill up the communication buffer of the blast command somewhere between the socket and the MCE itself.A workaround would be to limit the repeat-key-rate, but I don't know if it's already possible in the current IRSS (does anyone here knows?).A cleaner solution would be to implement a blast-jam detection in the IRSS server that enables to discard the incoming blast request accumulating (I don't think it is implemented). This is not a straightforward change.&nbsp;You shouldn't be the only experiencing this kind of anoyance. I will try to have look onto your problem, but it won't be soon...&nbsp;For my curiousity, what is a WAF evaluation ?</blockquote>

[QUOTE="Starwer, post: 1111285, member: 149636"] Hi Ashley, You surely have a point. What probably happens is that the key-repeat is faster than the blast-command, leading to a traffic jam of the communication. the keystroke events fill up the communication buffer of the blast command somewhere between the socket and the MCE itself. A workaround would be to limit the repeat-key-rate, but I don't know if it's already possible in the current IRSS (does anyone here knows?). A cleaner solution would be to implement a blast-jam detection in the IRSS server that enables to discard the incoming blast request accumulating (I don't think it is implemented). This is not a straightforward change. You shouldn't be the only experiencing this kind of anoyance. I will try to have look onto your problem, but it won't be soon... For my curiousity, what is a WAF evaluation ? [/QUOTE]

Verification