>> > Curious what client is this that is violating the protocol. >> >> I heard it was a Java program. >> > > This is not surprising there are a proliferation of non-blocking > implementations, > probably approaching 10 different implementations now.
Do you think some of the implementations may not be appropriate if they behave like that discussed in this thread? If so, maybe it is worth to add a warning to the backend.
Given that java code is notorious for not reading warnings, I'd say no
That said I'd probably be in favour of a DEBUG mode that did warn.
