Repository navigation
⚡ Optimize JSON serialization in simple_seismic_server #183
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -109,10 +109,10 @@ def do_GET(self): | |||||
|
|
||||||
| def send_json(self, data): | ||||||
| self.send_response(200) | ||||||
| self.send_header('Content-Type', 'application/json') | ||||||
| self.send_header('Content-Type', 'application/json; charset=utf-8') | ||||||
| self.send_header('Access-Control-Allow-Origin', '*') | ||||||
| self.end_headers() | ||||||
| self.wfile.write(json.dumps(data, separators=(',', ':')).encode()) | ||||||
| self.wfile.write(json.dumps(data, separators=(',', ':')).encode('utf-8')) | ||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. By default, json.dumps has ensure_ascii=True, which serializes non-ASCII characters into Unicode escape sequences (e.g., \uXXXX). Since the response is encoded in UTF-8, setting ensure_ascii=False allows non-ASCII characters to be written directly as UTF-8 bytes. This reduces the serialized payload size and improves serialization performance, aligning with the goal of optimizing JSON serialization.
Suggested change
|
||||||
|
|
||||||
| def log_message(self, format, *args): | ||||||
| """Override to customize logging""" | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to RFC 8259 Section 11, no charset parameter is defined for the application/json media type. Compliant JSON is implicitly UTF-8. Adding charset=utf-8 is redundant and technically non-standard, and some strict clients might reject or misinterpret it. It is recommended to keep the header as application/json.