Changes between Version 4 and Version 5 of pjsip-doc/consider
- Timestamp:
- Feb 27, 2014 10:28:48 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pjsip-doc/consider
v4 v5 1 1 {{{ 2 2 #!rst 3 4 .. toctree::5 :maxdepth: 26 7 3 8 4 Development Guidelines and Considerations … … 176 172 177 173 178 Some considerations on pjsua2 C++ API are: 174 Some considerations on PJSUA2 C++ API are: 175 179 176 #. Instead of returning error, the API uses exception for error reporting 180 #. pjsua2 uses standard C++ library177 #. It uses standard C++ library (STL) 181 178 #. The performance penalty due to the API abstraction should be negligible on typical modern device 182 179 183 180 184 181 185 pjsua2 API for Java, Python, and Others182 PJSUA2 API for Java, Python, and Others 186 183 --------------------------------------- 187 The pjsua2 API is also available for non-native code via SWIG binding. Configurations for Java and Python are provided with the distribution. Thanks to SWIG, other language bindings may be generated relatively easily.184 The PJSUA2 API is also available for non-native code via SWIG binding. Configurations for Java and Python are provided with the distribution. Thanks to SWIG, other language bindings may be generated relatively easily. 188 185 189 186 The pjsua2 API for non-native code is effectively the same as pjsua2 C++ API. However, unlike C++, you cannot access PJSUA-LIB and the underlying C libraries from the scripting language, hence you are limited to what pjsua2 provides. … … 199 196 NAT Issues 200 197 ---------- 201 198 TBD. 202 199 203 200 TCP Requirement … … 211 208 Latency 212 209 ------- 213 210 TBD. 214 211 215 212 Echo Cancellation 216 213 ----------------- 217 214 TBD. 218 215 219 216