Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If default response type is JSON, do we need an auto serializer? #42

Closed
kgriffs opened this issue Jan 24, 2013 · 2 comments
Closed

If default response type is JSON, do we need an auto serializer? #42

kgriffs opened this issue Jan 24, 2013 · 2 comments

Comments

@kgriffs
Copy link
Member

kgriffs commented Jan 24, 2013

Need to figure out whether an auto-serializer is needed/necessary/should be encouraged for data APIs? If so, look into implementing as a before/after hook.

Also, benchmark WSME to see if it a viable alternative. Con: json-patch support may be wonky?

@lichray
Copy link
Contributor

lichray commented Apr 25, 2013

There is one question before this: do we support non-UTF-8 JSON? According to rfc4627, UTF-16/32 LE/BE JSON are valid. If we support them, then we need to handle encoding in auto serialization/(denationalization, possibly). I know the requests library does it, FYI.

@kgriffs
Copy link
Member Author

kgriffs commented Dec 3, 2014

Duplicate of #145

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants