On Thu, Nov 3, 2011 at 6:21 PM, Daniel Friesen <lists(a)nadir-seen-fire.com>wrote;wrote:
On Thu, 03 Nov 2011 18:16:43 -0700, Brion Vibber
<brion(a)pobox.com> wrote:
In that case the thing to do is to probably
remove the namespace entirely
and resolve 24781 as WONTFIX instead of FIXED. I don't think there's much
benefit to adding a namespaced mode if nobody's ever going to bother
using
it because it's not default.
;) or maybe LATER as in 'You'll get a namespace when we rewrite the api
and shit like "*" and "boolean": "" stop showing up in the
json fomat of
the api'.
Hehhehe. :)
For now I'll revert back to requireing the includexmlnamespace option, but
keeping the tweak so using that option still won't break other XML outputs.
Looks like it could still be useful on internal requests, say when
generating API data subsets to include in XMPP recentchanges (where it's
nice to distinguish your payload with a namespace).
-- brion