[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: some thoughts on libkio
From:       Stephan Kulow <coolo () kde ! org>
Date:       1999-12-06 22:54:46
[Download RAW message or body]

Simon Hausmann wrote:
> 
> That means we will depend on a running server process in order to have a
> working kiojob? (like with kfm)

No, the master slave should be restartable without notice. What I have
in
mind is:
app asks dcopserver
dcopserver asks kioslave (that's the slave without protocol specific
knowledge)
(kioslave may be started when not present)
kioslave forks, the new process dlopens kio_file.la if it's the first
  time invoked and waits for input by it's parent process
the kioslave sends back a ticket to the app
the app opens a socket (,crunches the address of it with the ticket) and
sends
  back to kioslave the address
kioslave pipes to the process and this one contacts the application.

The application (in form of libkio) can get only one slave per protocol
and can ask this one to fork itself for further requests. There the
managing qualities of libkio come to work :)

I'm not sure if this is the best solution, but this is what I found when
I thought about the problem :)

Greetings, Stephan

-- 
When your memory goes, forget it!

[prev in list] [next in list] [prev in thread] [next in thread]