Provide interfaces for Java classes
Reported by
gez...@gmail.com,
Aug 16 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.85 Safari/537.36 Steps to reproduce the problem: 1. Write a wrapper / compatible type for a libjingle type (e.g. org.webrtc.DataChannel) 2. Make sure that this type can be used everywhere the original type can be used 3. Make sure that the interfaceof this type is always compatible with libjingle, even if the libjingle API changed What is the expected behavior? It would be great if there were interface definitions for all main types in the Java implementation of WebRTC. That would make it possible that compatible implementations (e.g. a data channel wrapper that does chunking / encryption / something else) can be used everywhere the main class can be used, as long as the interface is compatible. What went wrong? There are no interfaces in the Java implementation. Did this work before? No Chrome version: 52.0.2743.85 Channel: n/a OS Version: Arch Linux Flash Version:
,
Aug 17 2016
Marking the above issue as Untriaged as this is a new feature request. Dev team will take a call on the above issue. Thank you!
,
Aug 17 2016
perkj@ can you provide information about the feasibility and/or plans of implementing such a wrapper?
,
Aug 17 2016
This has nothing to do with Chrome right and should be filed in bugs.webrtc.org? We have Android Java wrappers for Datachannels but have no generic Java support for all platforms and we have no plans to add it as far as I know.
,
Aug 17 2016
Thanks Per. Good point regarding the bug tracker. Closing this (feel free to file a similar bug at bugs.webrtc.org). |
||||
►
Sign in to add a comment |
||||
Comment 1 by gez...@gmail.com
, Aug 16 2016