Sorry for the late response Lukas.
On 2014-06-16, Lukáš Fryč wrote:
Hey guys,
I was looking into AGPUSH-720 and I got an perception that not all error
response do we actually know on the client-side.
We should establish a common pattern - contract between server and client -
which says how is a failure message transported from server to client, e.g.:
- response header
- response message body /w given structure
Speaking about a contract between client/server what would you suggest?
Maybe we can start a gist for these definitions once it affects other
clients?
Right now, I've opened a PR for a generic failure handling mechanism that
can catch and report any error:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/226/files
I've already commented on that, overall looks good.
I plan to extend this error handling code dynamically as needed based on
response codes (e.g. 404=Request resource is missing) and contract
mentioned above ^.
Wdyt?
~ Lukas
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj