Re: GObject-based streams redux
- From: Jody Goldberg <jody gnome org>
- To: Mikhail Zabaluev <mhz altlinux org>
- Cc: gtk-devel-list gnome org, gnome-devel-list gnome org
- Subject: Re: GObject-based streams redux
- Date: Thu, 31 Jul 2003 17:01:25 -0400
On Fri, Aug 01, 2003 at 12:45:21AM +0400, Mikhail Zabaluev wrote:
> Hello Jody,
>
> On Thu, Jul 31, 2003 at 03:14:15PM -0400, Jody Goldberg wrote:
> >
> > libgsf has continued to mature and is now lgpl and used in several
> > applications. It's interfaces are all syncronous right now, but
> > adding some async api would be useful.
>
> libgsf is way overkill for my needs.
> All I need is a cute little abstract class (let's call it GIOStream)
> so that I can subclass it into 1) plain TCP sockets,
> 2) SSL sockets, and be able to plug both into a cute little library
> that takes whatever passes for a GIOStream. All other users
> of GIOStream would automatically become able to use the socket
> classes as well.
> What I don't want is the whole might of the structured file
> library and its dependencies bound to my little app,
> that's for sure.
>
> So, the question stands: is there any draft of a lightweight
> generic stream I/O framework that would be dependant only on
> the core glib and GObject?
gsf is a teeny tiny little lib, I wouldn't worry about size. The
core api GsfInput is probably not a good match for what you're after
though as it blends read and seek into one interface. For gsf-2.0
those will be split, but I haven't started on that change as yet.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]