Issue 4410: Current restrictions (ots-structs-ftf) Source: University of Newcastle upon Tyne (Dr. Mark Little, m.c.little@ncl.ac.uk) Nature: Uncategorized Issue Severity: Summary: There is an implicit assumption in the current text that all Current objects are available in all environments. This may not be the case, and we should allow for the fact that some environments may wish to restrict the Currents that are available. Resolution: see above Revised Text: Note: some implementations of the service may wish to restrict which implementations of Current are available. For example, in a pure client environment, only the CosActivity::Current implementation makes sense. Therefore, an implementation need not make all such objects available in all environments, and resolve_initial_references will behave accordingly. Actions taken: July 12, 2001: received issue May 2, 2003: closed issue Discussion: Resolution: It should be possible to restrict the availability of the various Currents used by the service. End of Annotations:===== From: "Mark Little" To: "XOTS FTF" Cc: Subject: Current restrictions Date: Thu, 12 Jul 2001 15:15:40 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Filter-Version: 2.1 (cheviot3) Content-Type: text/plain; charset="iso-8859-1" X-UIDL: ni2e9c~#!!!>3!!P^Xd9 There is an implicit assumption in the current text that all Current objects are available in all environments. This may not be the case, and we should allow for the fact that some environments may wish to restrict the Currents that are available. Mark. ---------------------------------------------- Dr. Mark Little Transactions Architect, HP Arjuna Labs Email: mark@arjuna.com | mark_little@hp.com Phone: +44 191 2064538 Fax : +44 191 2064203