|
I have been thinking about the specification for
unsolicited notifications in the Java api draft version 12.
The draft has two methods in LDAPConnection
that are concerned with Unsolicited Notifications:
one sets a flag indicating whether to keep or discard
unsolicited notifications:
setUnsolocitedNotifications(boolean flag)
the other gets the value of the flag
Unsolicited notifications are retrieved by calling
the getResponse(0) method from one of the
Listener classes. the "0" indicates message ID 0.
The problem is that a listener has association with
a connection only when a request is in progress
using that listener. A listener in an application with
5 connections open could be servicing requests
on all five connections or on none of them. Using
getResponse from the listener class to get
Unsolicited notifications is problematic. If no requests
are outstanding on the listener, there is no association
with a connection, so it is not possible to check
for unsolicited notifications.
It would seem that the only reliable way to check for
and get unsolicited notifications would be through
the LDAPConnection class itself and not through the listener.
classes. Two more LDAPConnection methods - ugh, but
perhaps necessary?
Anyone have any better ideas?
-Steve
------------------------
Steve Sonntag Novell, Inc., the leading provider of Net services software |