From kde-core-devel  Sat Apr 15 14:46:02 2006
From: Ralf Habacker <ralf.habacker () freenet ! de>
Date: Sat, 15 Apr 2006 14:46:02 +0000
To: kde-core-devel
Subject: Re: KProcess overhaul
Message-Id: <4441072A.6020803 () freenet ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114511343627623

Oswald Buddenhagen schrieb:
> On Sat, Apr 15, 2006 at 01:47:12PM +0200, Ralf Habacker wrote:
>   
>> Also after rereading the thread "KProcess overhaul", you have started 
>> I'm not sure, what you exactly means with this. Seems we have to collect 
>> the requirement for the planned KProcess. I mean KProcess should have 
>> the following functionality or speeking in use cases:
>>
>> 1. it should be able to start child process in blocking an non blocking 
>> mode
>> 2. it should be possible to provide the child process with specific  
>> command line arguments and a specific environment
>> 3. it should be able to set the working directory of the started child 
>> process
>> 4. it should be able to send data to the child process stdin
>> 5. it should be able to get data from the child process stdout and stderr
>> 6. it should be able to terminate child processes
>> 7. it should be able to get a signal on child process termination
>>
>>     
> 8. it should be able to connect multiple processes with each other,
> without the parent process being involved past the process creation.
> mkisofs|cdrecord type of things, you know.
>   
Isn't this the main task of inter process communication ussing pipes or 
shared memory ?
> 9. on unix, it should be able to deal with ptys
>   
Can you explain a non unix user for what this is good ?
> 10. it should be able to do arbitrary redirections without overhead,
> which is just a generalisation of 8 & 9.
>   
Ralf