-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate all SSE classes in io.reactivex.netty.protocol.text.sse #209
Comments
I have this mostly done. What I did was move the existing classes and replaced them with proxies that extend the originals. These proxies are marked as deprecated. |
@gorzell sounds good, I will wait for your PR then. In case I need to release 0.3.12 sooner, will punt this to 0.3.13 |
I'll try to wrap this up today. It has been a bit tricky because some tests fail sporadically for me and the Context tests still fail every time. |
ReactiveX#205 (Move SSE related classes to http): This is a new implementation of SSE for some optimizations and spec compliance. ReactiveX#209 (Deprecated all SSE classes in text pkg): SSE is only applicable to HTTP. ReactiveX#220 (SSE Output confusion): Default case only emits data event. ReactiveX#222 (Improved SSE API): Better construction semantics. ReactiveX#30 (Optimized SSE decoder): Rewrite of the existing decoder.
In relation to issue #205 we need to first deprecate these classes in the io.reactivex.netty.protocol.text.sse package so that we can delete some and move the other to the io.reactivex.netty.protocol.http.sse package in the next release.
The text was updated successfully, but these errors were encountered: