Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!CORY.BERKELEY.EDU!dillon From: dillon@CORY.BERKELEY.EDU (Matt Dillon) Newsgroups: comp.sys.amiga Subject: Re: IPC - A proposal Message-ID: <8803091817.AA18212@cory.Berkeley.EDU> Date: 9 Mar 88 18:17:46 GMT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 38 > >dillon@CORY.BERKELEY.EDU (Matt Dillon) says: > >> You guys don't think big enough! Don't use an exec message >> structure, use an exec IOStdReq request structure (which is headed by >> an exec message structure). ...... > >What in the Guru's name would that buy you? We aren't interested in all >the baggage that goes into an IO request. Just a standard basic message >structure that will prevent misunderstanding between programs, and will be >easy for people to incorporate into their stuff. It buys you generality, that is what it buys you. Think man! It makes everything so @#$!@$ easy if you use a IOStdReq (or similar) structure. Look at all the problems people have had with devices because the designers didn't stick to generic base structures (an IORequest is the base structure, but inadequate. The IOStdReq should have been made the base structure). And now you want to do what?!! An IOStdReq has all the necessary message junk, you can use other fields (like io_Offset) for other purposes, and it's big enough that most commands will be in a STANDARD EASY TO USE format. It is, in fact, a very compact and useful structure. I don't want to have to use ten thousand different custom structures when I use this system! I want to be able to (write/use) a RUN TIME LIBRARY to handle MOST FUNCTIONS SO I DON'T END UP WRITING 5000 LINES OF CODE TO SUPPORT THE G*D*MN SYSTEM! For instance, sending and receiving messages, creating message ports, basic functions, masking of unwanted or unsupported messages, searching for named ports, disconnecting, etc... should all be placed in a RUN-TIME library and NOBODY should make assumptions as to what it does.... just that you now have a port that you can receive messages on (etc...). > -- Pete -- -Matt