I hadn't realised that it was XHTML,( not ever having tried to parse it :) ) no problem then for those that prefer XML over Json in the browser. Thanks Ian
On 24 May 2011 18:01, Tobias Bocanegra <[email protected]> wrote: > hi ian, > the html response is actually xml compatible. the advantage using such > a response is that it is easy parseable by browsers as the response to > a form post by simple dom operations. > > regards, toby > > On Tue, May 24, 2011 at 5:06 AM, Ian Boston <[email protected]> wrote: >> I am wondering: >> >> How useful is the html response ? >> Its hard to parse, and not really something that a end user wants/needs to >> see. >> >> Might it be better to deprecate it entirely and respond with json or >> xml that can be processed by the client. >> >> I know in the app we have, we never look at the html, try to parse it >> or display it to the user, but then our use cases is not everyones. >> Ian >> >> >> On 24 May 2011 12:42, Bertrand Delacretaz (JIRA) <[email protected]> wrote: >>> Deprecate org.apache.sling.api.servlets.HtmlResponse >>> ---------------------------------------------------- >>> >>> Key: SLING-2087 >>> URL: https://issues.apache.org/jira/browse/SLING-2087 >>> Project: Sling >>> Issue Type: Bug >>> Components: API >>> Affects Versions: API 2.2.0 >>> Environment: This class is now replaced by >>> org.apache.sling.servlets.post.HtmlResponse, for now we should keep the api >>> one around but deprecate it. >>> Reporter: Bertrand Delacretaz >>> Priority: Minor >>> Fix For: API 2.2.2 >>> >>> >>> >>> >>> -- >>> This message is automatically generated by JIRA. >>> For more information on JIRA, see: http://www.atlassian.com/software/jira >>> >>
