DJI CloudAPI 1.9.0 versioning
Completed
I'm wondering, why this update only got a minor version update. I think there are a couple of breaking changes:
- Backend project structure changed, which makes it hard to follow the _real_changes
- Livestream configuration now in backend and frontend necessary
- New WebRTC service 4 (WHIP) requires new external server (or locally installed SRS)
- Absolutely no documentation regarding WebRTC mode 4
All in all I think this would have been not a bad idea to indicate that by a major version change.
-
You can submit your requirements at the following link, and we will forward them to our development team for investigation. https://sdk-forum.dji.net/hc/en-us/requests/new -
> I'm sorry, I misspoke. The current SRS on the dock does not support HTTPS.
This is not the only flaw. As far as I can see SRS is also not supported in Pilot2 and there are no plans to change that.
> You can submit your requirements at the following link, and we will forward them to our development team for investigation. https://sdk-forum.dji.net/hc/en-us/requests/new
Nah, this is wasted effort. I'm not going through this revolving door anymore
-
I went over your comments and posts, here and on Github, they are hilarious, thank you!
-
I apologize for the confusion earlier. Currently, our dock supports WebRTC + HTTPS only for Dolby. As for SRS, it doesn't support WebRTC + HTTPS on the dock just yet. The reason Dolby has HTTPS functionality is that we previously received requests from users, hence the dock enables the use of HTTPS features on Dolby specifically. Regarding your request for SRS, we've already communicated it to our R&D team, but there isn't a current plan in place for this feature. After you submit your requirement, we'll certainly pass it along to our development team and request them to evaluate the feasibility of adding this feature. Thank you for bringing this to our attention! -
For the issue you've raised on GitHub, we've already forwarded it to our R&D team. However, it's worth mentioning that the primary purpose of the demo design is to serve as a reference for developers, which means this particular issue might not be addressed with the highest priority. Nonetheless, your feedback is valuable to us, and we appreciate your contribution! -
> However, it's worth mentioning that the primary purpose of the demo design is to serve as a reference for developers, which means this particular issue might not be addressed with the highest priority.
Of course, yes, I didn't expect that. I just was expecting _some_ response in time. Other than that, I think to remember, that CloudAPI is advertised with the slogan "Why inventing the wheel twice?" and that you are claiming to make developer's life easier by providing 99% of the tasks already and the particular drone developer just has to do some re-branding and H5 stuff.
Turns out - not the case. No surprise BTW, I'm used to see that kind of banana-ware from DJI
-
Sorry about that! Our provided demo code is merely for your reference and inspiration, so feel free to edit and build upon it to suit your needs. We've already gathered and are currently evaluating the issue within our team. Also, when we say the Cloud API helps avoid reinventing the wheel, we mean it's relatively easier to use the Cloud API compared to developing apps with MSDK when it comes to customizing the push of data to the cloud. -
OK, but this is heavily depending on database operation and backend services. So you can't just say, you made that all "just for reference". At least not the backend. The entire CloudAPI is for bin, if the backend doesn't work exactly as it is supposed to work in your code. Hence you are obliged to care about functionality issues, at least with the backend. And not only lean back and say it wasn't meant like so.
Please sign in to leave a comment.
Comments
27 comments