|
Title: Big problem...with v9.50 and Gate Post by: ISIGest on January 17, 2019, 10:30:28 AM I see that you have splitted the project moving into Legacy the gateway, this is a big problem with future support...
In my app I use this components and now you moving into a deprecated section? What I must think for the future? Title: Re: Big problem...with v9.50 and Gate Post by: K. Okada (RTC) on January 17, 2019, 02:07:15 PM If your app is built on RTC Gateway components,
you'd better start looking for an alternative. You have some grace period , because your application built with the latest RTC SDK v9.50 and your current development environment would work for the time being. We've decided to drop some components off from RTC SDK. so that we can focus on maintaing our core components. The future is in the core HTTP components,(with coming HTTP2 support) and we would go forward with those users who develop HTTP server apps with RTC SDK core components. Once decided, we want to inform you the risk clearly as soon as possible and give you the time to prepare . This is how some components are marked "legacy" in the last release. Title: Re: Big problem...with v9.50 and Gate Post by: ISIGest on January 17, 2019, 04:04:38 PM This is a very discutible decision!!!
When I start to develop my application I use RTC to handle http request between gateway functionality on same server and on same port!! If I want to use an alternative to handle websocket requests to replace gateway I need to use another port on my server to handle websocket and work with rtc...or not?? This is a very cost for me to reconfigure all my customers installations and to develop this alternative. I need to find an alternative for replace completelly rtc. |