Welcome to my blog
I write about tech stuffs I find interesting. It’s possible you might find them interesting too. So, if you do, enjoy!
In the previous article, we covered the Message Queues IPC mechanism. This article will cover another one called Shared Memory.
In the previous article, we covered Unix Signal and its usage for IPC. An implementation of a popular asynchronous communication pattern will be covered in this article.
In the previous article, we covered Unix Socket and how it can be used for Inter-Process Communication. This article discusses a different and limited form of IPC.
In the previous article, We discussed the Named Pipes mechanism to achieve Inter-Process Communications. This article will cover another one called Unix Domain Sockets.
In the previous article, We introduced Inter-Process Communication and its different mechanisms. We’ll start with the first, Named Pipes or FIFO file!
Have you ever thought of how two processes can communicate in one device?
This is part two on how to write an OAuth client and server. If you have not read Part One yet, you should take a look at it.
OAuth (Open Authorization) is an open standard for access delegation, commonly used for internet users to grant websites or applications access to their information on other websites without giving them the passwords. It’s quite a mouthful, right? That’s the definition from Wikipedia for the specification behind the Login With Facebook, Login With Google, and Login with [Fill In Popular Site] buttons we see whenever we want to register or login into our various web accounts.
This post is for those who are interested in the internal details of the BitTorrent protocol.
subscribe via RSS