[unios] Re: Generic Design

[Anders Petersson]

From: Anders Petersson <anders.petersson@mbox320.swipnet.se>

At 13:51 1998-12-11 , you wrote:
>From: Pieter Dumon <Pieter.Dumon@rug.ac.be>
>
>> The same thing would be possible with my model, and even to a higher
>> degree. Since objects can support many formats (just add an interface for
>> each format), it would be possible to read HTML files or Word files as
>> usual text files - and the one who's reading doesn't have to add support
>> for it in any way. 
>
>That's easy to implement on POSIX too, and you can hide teh details from
>the user too. And with POSIX, it is far more easier to apply multiple
>filters or transformers to an input stream (file) in serie or in parallel
>to one file. Your design needs to switch between OH's to achieve this. 

Is that really easier with POSIX? I don't see why. Of course different OH's
are needed to accomplish anything like this... There's no way even POSIX
can avoid this.
If what you mean is my previous example, in fact only one OH is needed - it
can both support exporting text as the original format and some general
format... it's up to the OH.

>> If you have a list object type, you can take the output
>> of one program and feed it - in the form of a list - to another program.
>> Everything that can be done by piping in Unix can be done just as good with
>> my method, and often better.
>
>But what you descrive __IS__ POSIX !

What I described *is* not POSIX. It may resemble POSIX, but it is not the
same. In what formats can POSIX pipe information? Is it text and binary, or?

>> >> but I can't say it's just Posix with a different name...
>> >I'm not saying it's POSIX, I'm saying it can be done more effectively,
>> >more powerfully and more flexibly with POSIX. Add the power of X to
>> >this... 
>> 
>> Add the power of *my GUI* to what I've said, and I think it would well
>> out-weight Unix power/flexibility.
>
>Have you allready _used_ networked X ?

Nope. But since I can't imagine (I can be wrong) a single example of
networking which would be hard to solve with my design... I don't think it
can be less good than networked X. And, I heard some critizism to X some
time ago... so I guess it's not perfect.

>> The trumph card of my model is that there are not much of necessary APIs.
>> Most of the interfaces on a standard system lays outside the static part
>> (the kernel).
>
>I don't think the kernel shouyld be static. I know all OSs up to day use 
>a static model, but...

I'm open to everything, as long as it proves to bring bigger advantages
than disadvantages.

binEng

------------------------------------------------------------------------
To unsubscribe from this mailing list, or to change your subscription
to digest, go to the ONElist web site, at http://www.onelist.com and
select the User Center link from the menu bar on the left.
------------------------------------------------------------------------
UniOS Group
http://members.xoom.com/unios