TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Wed, 22 May 2002 14:01:16 +0200
Reply-To: Laurent Pautet <[log in to unmask]>
From: Laurent Pautet <[log in to unmask]>
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]> from "C. Daniel Cooper" at May 17, 2002 04:23:29 PM
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Parts/Attachments: text/plain (17 lines)
| 1) Alternative Implementations
| ------------------------------

Your specification does not indicate which side is in charge of
notifying an event. It may be one of the reasons why there are so many
specifications of the "same" service. You should have a look at the
COS Events (CORBA Object Services). In fact, there are four ways to
define the different interactions between a consumer and a
producer. IMHO, you cannot easily write such a service with only one
(or even few) access-to-subprogram type. You will need many of them
and this may become difficult to handle them manually (like a
combinatory explosion). Therefore, it is much easier to use OOP and to
have several primitives of only few access-to-object types.

--  Laurent