Re: [websocket] proper SPI for encoder/decoder instantiation?

Here it is https://bz.apache.org/bugzilla/show_bug.cgi?id=65262 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: [websocket] proper SPI for encoder/decoder instantiation?

On 22/04/2021 18:44, Romain Manni-Bucau wrote: Le jeu. 22 avr. 2021 à 17:32, Mark Thomas a écrit : On 22/04/2021 16:24, Romain Manni-Bucau wrote: Hi, Is it possible to reuse/add/have a SPI to create ws coders/decoders? Currently it is a hardcoded factory doing a "new"

Re: [websocket] proper SPI for encoder/decoder instantiation?

Le jeu. 22 avr. 2021 à 17:32, Mark Thomas a écrit : > On 22/04/2021 16:24, Romain Manni-Bucau wrote: > > Hi, > > > > Is it possible to reuse/add/have a SPI to create ws coders/decoders? > > > > Currently it is a hardcoded factory doing a "new" > > (org.apache.tomcat.websocket.Util#getDecoders

Re: [websocket] proper SPI for encoder/decoder instantiation?

On 22/04/2021 16:24, Romain Manni-Bucau wrote: Hi, Is it possible to reuse/add/have a SPI to create ws coders/decoders? Currently it is a hardcoded factory doing a "new" (org.apache.tomcat.websocket.Util#getDecoders for decoders, for encoders it is a bit worse since there is an instance as a

[websocket] proper SPI for encoder/decoder instantiation?

Hi, Is it possible to reuse/add/have a SPI to create ws coders/decoders? Currently it is a hardcoded factory doing a "new" (org.apache.tomcat.websocket.Util#getDecoders for decoders, for encoders it is a bit worse since there is an instance as a check here