> * I think Microsoft COM (and DCOM) may be another piece that addresses a lot > of what you were talking about with RPC. It allows transparent remote > procedure call, divides functionality into separate interfaces and deals with > versioning, extensible interfaces and also provides a factored means to > marshal (encode and decode) function interface parameters and results. I > haven't really used that in years, and probably things have moved on, but I > remain quite influenced by it. While it's quite sophisticated (read: > complicated) it's also quite comprehensive - there's a lot of depth there. > Possibly you won't use it directly, but it might be a good thing to study, as > it will be complementary to the things that Plan 9 does.
The older I get, the more I appreciate the COM interfaces in Microsoft. I was not exposed to the windows stack early on but in the last several years have been working in it. Interop is so cool, the only other thing I can think that is similar. One system I have been enamored with of late is the Erlang/BEAM VM. It's RPC procedures may be worth looking at. It's such a nice system, and I find myself favoring a more 'batteries included' approach these days. It's interesting to me how there are parallels between the Erlang stuff like servers and a plan9 server. Of course they're not totally the same, Erlangs focus is really on message passing / actor system but again, it's very interesting. Though this is certainly a forum for discussing plan9, i'd recommend everyone take a look at Erlang for building cool distributed systems. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T4b6cbcbd1021df9b-M3e069b93aedca8e841e28df7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
