Why not backport the IoFilter changes and go all out with a whole new SSL design for 2.1.X? Then give everyone 18 months of updates to 2.0.X before being deprecated.
On Tue, Mar 5, 2019 at 9:07 AM Emmanuel Lécharny <[email protected]> wrote: > > On 05/03/2019 14:19, Jonathan Valliere wrote: > > What in 2.1.X is not compatible with products build around 2.0.X? > > The difference lies in the API change in IoFilter interface (which > should not impact your code), and in the IoHandler interface, where the > addition of the event() method has been added. > > OTOH, if you don't use those methods, as they have default > implementation in abstract classes, you should be just fine. > > The biggest impact is when you want to check if a session is secured, in > 2.0 we were using a notification system, while in 2.1 we are using an > event. > > Note that 2.0 and 2.1 will evolve in parallel, with everything fixed in > 2.0 being ported to 2.1. If you prefer using 2.0.20, that will just work > fine. > > >
