[prev] [thread] [next] [lurker] [Date index for 2005/04/25]
> Anyhow, what I was thinking of when I said RPC was "any tool that > automatically generates local stub code for message passing." Hmmm, I'd lump that in with any other stub generator. So if the underlying message mechanism is queued then the call returns immediately, and you need to make another call later to get the reply? > I think that Linux has actually taken the best path here: they provide > a 'clone' system call which you tell exactly how much state you want to > share with the other thread (or process). Plan 9 fork() is rfork(RFNOWAIT|RFNAMEG|RFENVG|RFFDG|RFPROC), if I've got all my flags right. It's somewhere in the middle between share nothing and share everything. > >> Maybe. I still cling to the idea that type identification can be > >> useful, since everyone wants to do it, and everyone does it differently > >> and badly. > > As far as I'm concerned there's only been one lot that ever did that kind > > of thing correctly, and ironically they were a videogame company. > > FORM nnnn 8SVX NAME 000A "Pan Flute" AUTH 0011 "Electronic Arts" ... > So you mentioned. I never worked with AIFF format files, except as an > end user, so I don't have much practical experience there. Well, there's a lot of other IFF FORMs than AIFF. And that's really the important thing.There's stuff above here
Generated at 01:00 on 03 May 2005 by mariachi 0.52