sthustfo

asynchronous cancellation (when compared to deferred) is only recommended in scenarios where the thread does not share any data, semaphore or conditional variables with other threads. The target thread tends to cleanup any data within the thread cleanup handlers via pthread_cleanup_pop(). If not, the entire application might end up going down. Async cancellation has a very narrow application scope imho.

Large Language Model

any thoughts on how much resources 8x8 would be devoting to continued development of Jitsi? Given that you had pretty free run at atlassian.

It does not seem all that impossible now, now that Skype has been integrated into Facebook. From what I hear, they have stripped down most of skype and provided javascript apis for the facebook web app.

Before that, I always used to wonder how could one take all of signaling protocol (like the monstrous SIP, XMPP etc) and media (RTP) and cram all of it into the browser.

Well, I am not sure why Google went with XMPP when the rest of the telecom and networking industry is gravitating towards IETF SIP as signaling protocol. There are so may overlaps in both of them in the sense that they use the same components such as SDP and ICE. Can anyone from Google or otherwise throw some more light on

- Why Google prefers XMPP over SIP - In what areas XMPP is better that SIP

I am not stating that one is better than the other, but would like to understand the core differences and advantages.

Also with Google moving on with XMPP and other major vendors converging on SIP, where do you see the inter-operability issue heading towards?