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

List:       kde-core-devel
Subject:    Re: some thoughts on libkio
From:       Roberto Alsina <ralsina () unl ! edu ! ar>
Date:       1999-12-06 9:41:16
[Download RAW message or body]

On Mon, 6 Dec 1999, Lars Knoll wrote:

> > Yes, there are many things to do to make kio a really full featured I/O
> > library :)
> > 
> > But I would like to put your request in the queue and start with Waldo's
> > proposal of making kioslave one central server that forks itself and
> > dlopens
> > factories and libkio to handle the communication with the instances.
> 
> Sure. I just wanted to add these proposals now, since some support for
> pipelineing and persistent connections will be needed to make kio fast for
> http requests, and you seem to be restructuring kio anyway.
> 
> What I propose is mainly an extension to the existing protocol between
> slave and iolib. Slaves not supporting persitent connections
> or pipelineing would not need many changes (perhaps none at
> all).
> 
> I think, that this would not only make libkio much faster for http (and
> perhaps also for other protocols like ftp and pop), but also make the API
> simpler, since the programmer doesn't need to care about how many requests
> one schedules at the same time anymore, as I have to do up to
> now. This would mean, one would need some sort of scheduler in libkio to 
> distribute requests to the slaves.  

It's starting to look like Caitoo should be folded into libkio, isn't it?

 ("\''/").__..-''"`-. .         Roberto Alsina
 `9_ 9  )   `-. (    ).`-._.`)  ralsina@unl.edu.ar
 (_Y_.)' ._   ) `._`.  " -.-'   Centro de Telematica
  _..`-'_..-_/ /-'_.'           Universidad Nacional del Litoral
(l)-'' ((i).' ((!.'             Santa Fe - Argentina
                                KDE Developer (MFCH)
Not mad, but bound more than a madman is (Romeo and Juliet, Act I Scene II)

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