which, strictly speaking, breaks the xml-rpc spec. Other xmlrpc implementations are supposed to ignore such an
attribute (unless they implement a brain-dead custom xml parser...), so it should be safe enabling it in
heterogeneous environments. The activation of this feature is done by usage of an option passed as second parameter
which, strictly speaking, breaks the xml-rpc spec. Other xmlrpc implementations are supposed to ignore such an
attribute (unless they implement a brain-dead custom xml parser...), so it should be safe enabling it in
heterogeneous environments. The activation of this feature is done by usage of an option passed as second parameter