I've just noticed that xml node thread happily throws out XML for nodes that don't exist, and presumably also for ones that dont/cant have replies. I'd patch it not to, but I'm not sure what it should do instead: Return an HTTP error, go to the 'no such node' (aka Tough Beans) node, or just return an empty XML frame with no 'threads' tag ?

(Noticed while using davidos thread retitler, and passing it a 7-digit nodeid accidently.. ,)

C.

  • Comment on XML Node Threads for non-existant nodes?

Replies are listed 'Best First'.
Re: XML Node Threads for non-existant nodes?
by Arunbear (Prior) on Dec 02, 2004 at 15:55 UTC
    What about returning an error document, something like
    <?xml version="1.0" encoding="ISO-8859-1" ?> <error message="no such node"/>
Re: XML Node Threads for non-existant nodes?
by Aristotle (Chancellor) on Dec 19, 2004 at 16:51 UTC

    Just produce an empty frame — no need to create special cases for ticker clients to consider.

    Makeshifts last the longest.