You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Teams need access to non-C libraries to develop modern software. Based on conversations from the RDK Summit the protocol has been intentionally undocumented to prevent any other library offering support for the protocol.
That doesn't work for many modern languages that either cannot, or should not include c code.
We need a formal wire protocol definition so that the community can maintain the libraries and infrastructure needed.
Why does providing multiple language bindings not work?
Multiple language bindings are often based on a single .so library that is wrapped with glue code, but requires the external dependency. This causes problems for languages like go that need to be independent of .so files for portability reasons.
The text was updated successfully, but these errors were encountered:
Teams need access to non-C libraries to develop modern software. Based on conversations from the RDK Summit the protocol has been intentionally undocumented to prevent any other library offering support for the protocol.
That doesn't work for many modern languages that either cannot, or should not include c code.
We need a formal wire protocol definition so that the community can maintain the libraries and infrastructure needed.
Why does providing multiple language bindings not work?
Multiple language bindings are often based on a single .so library that is wrapped with glue code, but requires the external dependency. This causes problems for languages like
go
that need to be independent of .so files for portability reasons.The text was updated successfully, but these errors were encountered: