Re: [hybi] Restarting IESG review on permessage-deflate

[Joakim Erdfelt <[e-mail]>]

> Well, I'm sorry for the Java community not being able to fix this in 10+
> years;)
>

Yet, oddly, with web technologies, this hasn't been a problem since our
initial use of Oak in 1995 (yes, Jetty has existed since 1995)
Also, the opposite is true as well.
The capabilities of one set of libraries (c & python) should not be forced
on all environments as well.
The spec should not have these kinds of things mandated or required.
We have no problem with a spec having advanced features and configurables
such as these, but don't force them.



>
> > We are not using our own implementation of Deflate, as the one provided
> by Java itself is better performant (both in speed and memory use)
>
> I feel your pain, but:
>
> 1) Z_SYNC_FLUSH is available in Java now
> http://bugs.sun.com/view_bug.do?bug_id=4206909



This does not operate in the same way as what pywebsocket expects.  However
chromium's behavior is consistent (or resilient, hard to say)



>
>
> 2) FWIW, as a sidenote, here is a pure Java implementation capable of the
> respective features:
> https://github.com/ymnk/jzlib



Again, not performant, and uses too much memory, and is ultimately at odds
with precedents already set with other web technologies.
Remember, websocket is a web technology at its heart.
Imagine the opposite, a theoretical spec mandated something that would mean
you could not use your native implementations of something common, lets say
for argument that you suddenly were forced to, by a spec, to handle
filesystem metadata tags.
Now what?
do you toss out all of your standard file i/o and filesystem libs and start
anew?
do you force the entire environment ecosystem to catch up to
this theoretical spec?
do you introduce another file system library mechanism just to handle this
theoretical spec? having 2 filesystem libraries at the same time?

As you can see, these concepts might have value, for some, but should not
be forced or required.
These are advanced features, optional features.

- Joakim