Issues for Mailing list of the Lightweight Services Finalization Task Force

To comment on any of these issues, send email to lwservices-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 7619: Can we eliminate CosPropertyService.idl from Lightweight time
Issue 7674: Lack of non-normative client IDL definition

Issue 7619: Can we eliminate CosPropertyService.idl from Lightweight time (lwservices-ftf)

Click here for this issue's archive.
Source: Rockwell Collins (Mr. David Haverkamp, dahaverk(at)yahoo.com)
Nature: Uncategorized Issue
Severity:
Summary:

Can we eliminate the CosPropertyService.idl from the Lightweight time? or
at least make it optional or embedded system friendly?


I have some thoughts about it...  But, I'd like to hear what others think.
Obviously this would have to be something deferred to the RTF if we do it.


Obviously, I'm starting to think about some implementation issues with
Lightweight Services.


It seem to bring along alot of extra baggage...

Resolution:
Revised Text:
Actions taken:
July 28, 2004: eceived issue

Issue 7674: Lack of non-normative client IDL definition (lwservices-ftf)

Click here for this issue's archive.
Source: Raytheon (Mr. Gerald Lee Bickle, Gerald.L.Bickle(at)raytheon.com)
Nature: Uncategorized Issue
Severity:
Summary:

Based on the roles on clients that use the event service or naming service
only certain operations are used.
Recommendation: Add another annex for Client Non-Normative IDL for
Lightweight Services

Resolution:
Revised Text:
Actions taken:
September 3, 2004: received issue