Hello Planet KDE!
My name is Puneet Goyal. I am a B.Tech. 4th Year Student in Delhi Technological University, New Delhi, India. My GSoC Project is an Enhancement to Peer-to-Peer DBus for Telepathy DBus Tubes. My mentor Daniele is one of the most awesome person I have ever met. He has great DBus Skills and also did a GSoC Project last year on Telepathy Tubes and File Transfer in KDE.
You can find more about Telepathy and Telepathy Tubes here .
D-Bus Tubes allow you to share a private DBus between two or more clients, proxied over Telepathy.Telepathy is a flexible, modular communications framework that enables real-time communication via pluggable protocol backends. Telepathy is a communications service that can be accessed by many applications (“clients”) simultaneously.D-Bus is a message bus system, a simple way for applications to talk to one another.
When an application connects to a peer to peer dbus tube, it is difficult to know if an object is registered or unregistered. Even when it registers for another object, the other side of the tube must know about it. So the idea is to create a class that could ease the object to register and unregister on the DBus Tubes and access the information about it.It would even let us create and share as many objects as we need, for e.g, we may want to run a number of kwhiteboard applications and share them with other peers.
This might even be possible using introspection, but it is not a good way to implement it because there are no signals on the introspect interface, so it won’t be possible to know if other the remote side has registered some new object.Also,different channels and connection objects may offer different interfaces to each other, depending on the capabilities of the channel or connection, but that most of the implementations of D-Bus introspection assume that all objects of the same class will have the same interfaces.
These summer holidays are going to be a lot of fun and interesting