Changes between Version 8 and Version 9 of pjsip-doc/intro_pjsua2
- Timestamp:
- Feb 6, 2014 9:25:20 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pjsip-doc/intro_pjsua2
v8 v9 52 52 For platforms that require polling, the PJSUA2 module provides its own worker thread to poll PJSIP, so it is not necessary to instantiate own your polling thread. Having said that the application should be prepared to have the callbacks called by different thread than the main thread. The PJSUA2 module itself is thread safe. 53 53 54 Problem with Garbage Collection55 ------------------------------- 54 Problems with Garbage Collection 55 -------------------------------- 56 56 Garbage collection (GC) exists in Java and Python (and other languages, but we don't support those for now), and there are some problems with it when it comes to PJSUA2 usage: 57 57 … … 61 61 Due to problems above, application '''MUST immediately destroy PJSUA2 objects using object's delete() method (in Java)''', instead of relying on the GC to clean up the object. 62 62 63 For example, to delete an Account, it's '''NOT'''enough to just let it go out of scope. Application MUST delete it manually like this (in Java):63 For example, to delete an Account, it's **NOT** enough to just let it go out of scope. Application MUST delete it manually like this (in Java): 64 64 65 65 .. code-block:: c++