sthustfo

What are the typical use cases for the Guest VM to talk to Hypervisor? I see 2 use cases mentioned on the Proxmox link (https://pve.proxmox.com/wiki/Qemu-guest-agent)

1. shutdown the guest 2. freeze the guest system during backup/snapshot

Just curious about other possible use cases.

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.

You have nailed it perfectly regarding moving to cloud, on hindsight I think I was too vague.

And this is indeed a broad subject, with each issue tackled individually. I am asking for any suggestions on resources (books, articles, videos, podcasts etc) to follow to gain insight in this area. I would really appreciate it.

Thanks.

How does LibreSSL compare with boringssl (google's fork)?

It is basically WebRTC, but without SDP and Offer/Answer mechanism.

The service provides STUN and TURN servers to aid with NAT and firewall traversal, allowing the WebRTC services/apps to concentrate their energies on their core service delivery. Further, the service allows the WebRTC service providers to monitor, audit and enforce policies for each of their users.

Different boats, I agree. Skype is an additional plugin I think, so you don't need to have skype installed on your device. But that's the whole point. Google is the new Microsoft, though probably not as much evil. They have wide interests in almost all areas from search engine, android, chrome os, social, browser etc. So they can really control and push what fits their needs.

Tomorrow if Facebook comes out with their own browser, they would surely push skype baked in, into the browser rather than make it an additional installation.

When I mentioned the word "monstrous", I meant that in terms of the implementation and code size. I am not sure of XMPP, but SIP I think is. There are tons of new rfcs, specs and drafts that have come up which one has to implement for effective interoperable SIP sessions.

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.

Yet another thing I find amusing from Google is that the latest Android SDK has dedicated APIs for multimedia calls using SIP - http://developer.android.com/guide/topics/network/sip.html

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?