[Kde-pim] Proposal for a solution for bug 77862

Guy Maurel guy-kde at maurel.de
Sun May 30 18:17:00 BST 2010


Hi again!

On Monday 24 May 2010 22:13:42 Thomas McGuire wrote:
> Hi,
> 
> On Monday 24 May 2010 18:22:54 Guy Maurel wrote:
> > On Thursday 20 May 2010 19:27:33 Thomas McGuire wrote:
> >
> > > There are two different kind of timeouts: The first one is the timeout
> > > for waiting when reading or waiting to read from a socket. That is what
> > > I talked about earlier.
> > > The second timeout is the timeout until a KIO slave process gets killed.
> > > When KIO slave processes are not used anymore, they are kept around for
> > > some time
> > 
> > this is right.
> > this is the one we have to kill because we cannot use it anymore.
> 
> (I assume with "this is the one", you're refering to the KIO slave process 
> timeout)
> Why do you think the KIO slave has to be killed? Since the socket connection 
> seems to be the problem, disconnecting and then reconnecting should solve the 
> problem. Making the socket timeout lower ensures the the slave does not get 
> stuck and actually has the chance to disconnect, I assume.
> What am I missing here?
This idea is new for me. I'll work on it the next days...

-- 
guy
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/



More information about the kde-pim mailing list