Hacker News new | ask | show | jobs
by dugmartin 4096 days ago
This sounds a lot like CORBA (http://en.wikipedia.org/wiki/Common_Object_Request_Broker_Ar...).

The big problem with distributed classes is that network communication links are fragile and you need to bake how to deal with failures into your methodology. Erlang handles this in a way that Joe Armstrong explains here:

http://armstrongonsoftware.blogspot.com/2008/05/road-we-didn...

2 comments

It also brings up Fowler's First Law of Distributed Object Design: "Don't distribute your objects."
Not sure why it sounds like CORBA.

The point would be for an external system to handle communication.

I agree with what Joe says in that article.