On Mon, 31 Mar 2008, sridhar yerram wrote: > Date: Mon, 31 Mar 2008 18:49:56 +0100 (BST) > From: sridhar yerram <[EMAIL PROTECTED]> > Reply-To: <[email protected]> > To: <[email protected]> > Subject: [twincling] how xserver understands gnome protocols? > > Hello Friends,, > i would like to know the information how packets are processed by xserver > from gnome/kde... > i heard about xmon but iam unable to download it.. > my question how the opened graphical information is maintained by > xserver..where it stores , can we get that information...how about the events > performed on the window....can we grab those information the actions which > are performed on the window... iam developing a "Framework for Xserver Event > Collection " ..so on part of this i need this..things.. > > looking for your replies. > regards > sridhar gupta yerram >
Hi Sridhar: X window system protocol, ver 11 is also RFC 1013 http://tools.ietf.org/rfc/rfc1013.txt X11R7 protocol specification is here ftp://ftp.x.org/pub/X11R7.0/doc/PDF/proto.pdf As you know that X-window is a client-server protocol where client and server interactions are leveraged on a reliable, byte stream transport connections. X window has ICE or Inter Client Exchange protocol which provides a generic framework for building protocols ontop of X protocol. The key capabilities are: . basic mechanism for setting up/shutting down connections . authentication . version negotiation . error reporting Typically protocols run within an ICE connection and all of them share the same transport layer connection. Now, coming to the interaction between Xserver and KDE. This interaction will always be using X protocol and occur between XServer and KWin. KDE being a sophisticated Desktop Environment, has the following additional requirements. . interop between KDE apps . component service sharing . register for services . control apps using scripts DCOP or [D]esktop [CO]mmunication [P]rotocol is the innovation inside KDE that addresses all the above requirements and also serves as a rendenzvous point for services, components and registration mechanism. DCOP is built on top of the ICE protocol. It is accessible as a 'dcop' scriptable command. for example, to get the name of the wallpaper, type in shell command $ dcop kdesktop KBackgroundIface currentWallpaper 1 What makes DCOP unique is that, DCOP makes it possible to add "new" features that were never envisaged when an application was first created. So, tracing KDE packets so to speak, will require working with dcop. KDE has some real innovations and KDE 4 is absolutely mind blowing ! thanks Saifi.
