dcop services

Ian Reinhart Geiser geiseri at yahoo.com
Sun Oct 19 01:19:05 BST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 18 October 2003 05:39 pm, Tobias Koenig wrote:
> On Sat, Oct 18, 2003 at 12:02:07AM -0400, Ian Reinhart Geiser wrote:
> > On Sunday 12 October 2003 08:13 pm, George Staikos wrote:
>
> Hi Ian,
>
> > >   I don't know what scheme is best, but we have to have one.  Tying up
> > > ram like this is a bad idea, and really quite annoying.
> >
> > Since im basicly the author of both, and they are based off the same
> > basic template, it would be trivial to add a timeout from a last access
> > point of view.
>
> But then an application has to check if the dcop service is available
> whenever it tries to access a service and restart it when necessary...
>
as it should be already, so its not a problem.

> > I have toyed with this for a while, but was wanting to attack this
> > problem more in the dcop server end of things.
>
> ... can the dcop server handels such cases?
Ideally, but everytime I look into this, it seems that the changes to the dcop 
server are kind of invasive.  What I had envisioned, was every time an 
application made a dcop call that went through the server the server would 
make note of the caller and would use that to increment the refcount for the 
dcop connection.  When the caller unregisters from the server, then the 
refcount goes down.    Where I got stuck was how to have the client ask the 
dcop server "hey is there anything still registerd that has talked to me?".

i might take some time and look at this issue later this winter, but now time 
and energy is kind of keeping it as a small problem.


Cheers
	-ian reinhart geiser

- -- 
- --:Ian Reinhart Geiser <geiseri at yahoo.com>
- --:Public Key: http://geiseri.myip.org/~geiseri/publickey.asc
- --:Public Calender: http://geiseri.myip.org/~geiseri/publicevents.ics
- --:Jabber: geiseri at geiseri.myip.org
- --:Be an optimist -- at least until they start moving animals in 
- --:   pairs to Cape Canaveral. ~ Source Unknown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/kdh5Py62TRm8dvgRAnxeAJ9XeiFAHMXDeqdgyqDjj4IljuLS3wCfT0Yu
+FsZqWYljcOiIyDCJPQiHVc=
=tyVp
-----END PGP SIGNATURE-----




More information about the kde-core-devel mailing list