Re: The storage interface cleanup
- From: Miguel de Icaza <miguel helixcode com>
- To: Darin Adler <darin eazel com>
- Cc: Michael Meeks <mmeeks gnu org>, Bud Tribble <bud eazel com>, Andy Hertzfeld <andy eazel com>, <gnome-components-list gnome org>
- Subject: Re: The storage interface cleanup
- Date: 20 Oct 2000 16:17:55 -0400
> > I am talking about the IDL changes, which are sort of frozen beginning
> > with GNOME 1.4. After this point, the interfaces will be published,
> > and the only real fix would be to have two interfaces for streaming
> > (Stream and Stream2, PersistStream and PersistStream2, Storage and
> > Storage2, PeristStorage and PersistStorage2) and applications would
> > have to support them both.
>
> They could support them both, if we needed to be compatible with old
> components. But I don't see why you say they would *have* to support them
> both.
It seems like a lot of pain inflicted on everyone for the sake of
a few changes to Nautilus as Dietmar pointed out.
> We could require revving both components and applications at the Gnome 2.0
> time frame. I understand you don't *want* to do that, but I haven't heard
> any specific reasons why it's such a terrible idea.
Because it is lame. I had hoped you could figure why this is lame,
but I will explain:
* Because not every component might transition to supporting
the two interfaces at the same time.
* Because I will hate to tell people `we have a kickass
component architecture', `oh, and btw, and you have to
implement streams twice, and storages twice, but never mind
that'. Which just sounds retarded.
* Because of each of the 4 possible combinations that
components might support, half of it is a losing
combination.
* Because we can not have a UNIX component architecture if
every application is going to have a different set of
interfaces it will support.
Miguel.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]