Issue 4255: MOF IDL rules to minimize network roundtrips (mof-rtf)
Source: DSTC (Dr. Stephen Crawley, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: Various people have complained that retrieving meta-data (typically
features of Classes) using the IDL produced by the MOF IDL mapping
involves too many round-trips.  This is preventing people from using
MOF generated IDL in projects.  This issue calls for a solution (or
solutions) to this problem.

Resolution: 
Revised Text: 
Actions taken:
April 6, 2001: received issue
Discussion: 
This issue was raised at the Irving MOF-RTF meeting by (I believe)
Dave Frankel.  The proposal from that meeting was:

"Consider integrating XMI and MOF such that the interface allows
packaging up the features needed and the corresponding values as an XMI
document. This has the advantage customizing the set of features
returned.

Alternately extend the reflective interfaces to return get_all_features. 
Or get_requested_features(featurelist, featurevaluelist)"

I would add a third alternative, which is to define an IDL mapping
Tag that tells the mapping to generate a 'meta-model specific' 
get_all_features (or equivalent) operation for the interface(s) for
a tagged Class.

Also, I think we should consider adopting all three approaches. 
This issue was raised at the Irving MOF-RTF meeting by (I believe) Dave Frankel. The proposal from that meeting was: "Consider integrating XMI and MOF such that the interface allows packaging up the features needed and the corresponding values as an XMI document. This has the advantage customizing the set of features returned. Alternately extend the reflective interfaces to return get_all_features. Or get_requested_features(featurelist, featurevaluelist)" 

I would add a third alternative, which is to define an IDL mapping Tag that tells the mapping to generate a 'meta-model specific' get_all_features (or equivalent) operation for the interface(s) for a tagged Class. 

Also, I think we should consider adopting all three approaches. 

It looks like Issue 2876 is talking about this problem, as is Issue 3411. 


End of Annotations:=====
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: mof-rtf@omg.org, issues@omg.org
Subject: MOF IDL rules to minimize network roundtrips
Mime-Version: 1.0
Date: Fri, 06 Apr 2001 09:35:23 +1000
From: Stephen Crawley <crawley@dstc.edu.au>
X-Scanned-By: MIMEDefang 1.0
(http://www.roaringpenguin.com/mimedefang/)
Content-Type: text/plain; charset=us-ascii
X-UIDL: ##1e9WS&!!3KG!!%%hd9

Source: DSTC (Dr. Stephen Crawley, crawley@dstc.edu.au)
Nature: Uncategorized Issue
Severity:
Summary: 

Various people have complained that retrieving meta-data (typically
features of Classes) using the IDL produced by the MOF IDL mapping
involves too many round-trips.  This is preventing people from using
MOF generated IDL in projects.  This issue calls for a solution (or
solutions) to this problem.

Discussion:

This issue was raised at the Irving MOF-RTF meeting by (I believe)
Dave Frankel.  The proposal from that meeting was:

"Consider integrating XMI and MOF such that the interface allows
packaging up the features needed and the corresponding values as an
XMI
document. This has the advantage customizing the set of features
returned.

Alternately extend the reflective interfaces to return
get_all_features. 
Or get_requested_features(featurelist, featurevaluelist)"

I would add a third alternative, which is to define an IDL mapping
Tag that tells the mapping to generate a 'meta-model specific' 
get_all_features (or equivalent) operation for the interface(s) for
a tagged Class.

Also, I think we should consider adopting all three approaches.