[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ANNOUNCE] Introducing Codezero

From: olafBuddenhagen
Subject: Re: [ANNOUNCE] Introducing Codezero
Date: Fri, 7 Aug 2009 19:29:30 +0200
User-agent: Mutt/1.5.19 (2009-01-05)


On Wed, Aug 05, 2009 at 11:15:06AM +0300, Bahadir Balban wrote:

> OK, by object-based I mean a CORBA-like distributed computing
> architecture where object instances are defined on the server side,
> and clients refer to those object instances by references to them
> (sometimes by using their memory address as a key). In this model, the
> client uses an interface definition language in order to generate
> boilerplated code to access or refer to methods available on the
> remote object.
> The key points here are that;
> * Programing is done in object-oriented fashion.

> * Objects are created, and accessed by *automated* methods such as an
> OO  programming language, IDL compilers, stub generation etc.
> My idea in a nutshell is to remove the initially described methods of
> creating, managing, referring to objects, (as I find them to
> complicate design) and define ad-hoc, or loosely defined resources,
> but continue to protect them by capabilities. These resources can be
> thought of as objects, but only conceptually, rather than being
> created by automated tools such as an OO programming language or IDL
> compiler.
> But back to my conclusion with objects, in the above example model,
> instead of using automated methods of creating, referring, managing
> objects, the number of resources protected are reduced to a minimum
> set. Also, the set of operations allowed on them are reduced to a
> minimum set. The protection is still there, but the resources are
> defined with an optimized, hand-crafted engineering method instead of
> using automated tools, thus reducing the complexity.

IDL complilers have nothing to do with managing objects... Or at least
MiG doesn't. (Don't actually know any others.)

The purpose of the IDL compiler is simply automating creation of code
for handling data structures sent in an IPC (marshalling), and
dispatching different types of requests on the server side. It does so
by generating code from a simple interface definition. It doesn't define
any resources, create any objects, or anything like that.

I wonder, have you ever looked at what MiG actually does?...


reply via email to

[Prev in Thread] Current Thread [Next in Thread]