Inclusion of documentation in introspection data?

[John (J5) Palmieri]

I was thinking of adding it as an annotation.  In fact python can do
this without spec changes if we want to.  We eventually wanted to have
it so you could do print proxy_obj.__doc__ and get documentation.  The
biggest problem is bandwidth.  Good documentation can easily become
bigger than the introspect data itself.  Do we want to go down that
road?  

On Mon, 2005-10-24 at 16:23 +0100, Robert McQueen wrote:
> How do people feel about adding an optional tag to the introspection DTD
> to include documentation about the parent node, be it an object,
> interface, signal or method? In the Python bindings this could trivially
> originate from the __doc__ strings.
> 
> Regards,
> Rob
> _______________________________________________
> dbus mailing list
> dbus at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dbus

-- 
John (J5) Palmieri <johnp at redhat.com>