-
Notifications
You must be signed in to change notification settings - Fork 1
⚡ perf: optimize JSON serialization in simple_seismic_server #127
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
base: main
Are you sure you want to change the base?
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. To further optimize JSON serialization in line with the performance goals of this PR, consider adding Additionally, the PR description mentions replacing
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, the
application/jsonmedia type does not define acharsetparameter. JSON text is required to be encoded using UTF-8 for interoperability, making the; charset=utf-8suffix redundant and technically non-compliant with the MIME type registration. While most clients handle it gracefully, it is best practice to omit it.