You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
JSF seem to be criticized for having XML responses in AJAX requests. Those come from an older time of the JSF specification (as I know) and are today out-dated to use XML in HTTP responses. Modern MVC frameworks (like JSF is) use JSONs or RESTful responses (I know the former one).
This proposed change will drastically reduce the utilized bandwidth and "silence" critics directing this issue. :-)
The text was updated successfully, but these errors were encountered:
It's perhaps not always so super clear cut due to compression (XML compresses really well), but nevertheless a JSON response is absolutely in scope. I remember we discussed this before, but it didn't make the 2.2 or 2.3 cut.
JSF/PF are being criticized for having "fat" XML responses in AJAX responses. Sure you cannot make everything right for everybody. So let's bring it back and (maybe) assign it to 2.4 or 2.5 specification.
Of course, PrimeFaces are not the topic here, just mentioned it. I may have to bring it up over there, too then.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
JSF seem to be criticized for having XML responses in AJAX requests. Those come from an older time of the JSF specification (as I know) and are today out-dated to use XML in HTTP responses. Modern MVC frameworks (like JSF is) use JSONs or RESTful responses (I know the former one).
This proposed change will drastically reduce the utilized bandwidth and "silence" critics directing this issue. :-)
The text was updated successfully, but these errors were encountered: