Bug 2796

The Notification Spec(version 1.1, formal/04-10-13) defines default values for
several properties. For example:

2.5.5.5 Maximum Events Per Consumer

"... the default setting of this property is 0, meaning that
the proxy imposes no limits on the maximum number of events
that may be queued for its consumer."
 
Also, in the spec:
 "
 2.5.6.3 Use of get_qos()
 The get_qos operation can be used to determine the current QoS properties in
 effect for a notification channel, a proxy group admin object, or an
 individual proxy. It returns all properties and their values, including
 those initialized from higher levels,and those that were never explicitly
 set but have default values.

 From this paragraph, it appears that TAO is not compliant with the Notification
spec with regard to the default values.

Here are some results from my simple testing program:

We don't get returned property value from get_admin() without explicitly calling
set_admin() , but we do get returned property value from get_qos().  I did a
simple test of what TAO Notify Service gives us without calling set_qos() or
set_admin() explicitly, i.e., I create a notify event channel, then I call
get_qos() and get_admin() on that newly created channel immediately, after that
I call get_qos() on the created supplier admin and proxy consumer. See the
output I got:
"
the default QoSProperties of the event channel has length 1
the name of the QoS property: ThreadPool

the default AdminProperties of the event channel has length 0

the default QoSProperties of supplier admin has length 1
the name of the QoS property: ThreadPool

the default QoSProperties of the proxy consumer has length 1
the name of the QoS property: ThreadPool
"

From reading the spec, get_qos () needs to return a list of all QoS properties
which have default values. But TAO only returns one QoS property - "ThreadPool".

For get_admin(), the spec is a bit vague there. It doesn't talk about default
values as get_qos() does. Since it is not clear about the default values, we
should probably do just like what get_qos() does now.

3.1.5.1 get_admin
The get_admin operation takes no input parameters, and returns a sequence of
namevalue pairs that encapsulates the current administrative settings for the
target channel.