|
There should not be any interoperability issues with controls
if
we remove the newInstance method.
The SDK has responsibility for creating
the appropriate LDAPControl
object. How it creates it is up to the
implementation. Of course,
depending upon controls that might have been registered
the SDK
might have to call a constructor of an application specified
Class. But again
when and how this constructor get called is up to the
implementation.
Javed
>>> Rob Weltman <robw@worldspot.com> Thursday, January 25,
2001 3:16:44 PM >>>
That would kill interoperability. A SASL layer that worked with one implementation of the LDAP API would not work with another, and a control written for one implementation would not work with another implementation. Rob Steve Sonntag wrote: > There are several methods that an application will never use: LDAPConnection.setInputStreamLDAPConnection.getInputStreamLDAPConnection.setOutputStreamLDAPConnection.getOutputStreamLDAPControl.newInstance It is my feeling that these should not be defined in the Java API draft,even though functions like these may be defined as public insome implementations. These implementions use these in the API itself,but the application does not use them. These functions force an implementation style, but the draft should notforce any style of implementation. The draft should define only the applicationinterfaces. These methods should be removed from the draft. -Steve ------------------------ > Steve Sonntag > Novell, Inc., the leading provider of Net services software |