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.

Sign up for GitHub

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

Jump to bottom

Serialize request/response with BSON instead of JSON #11

Open
jjavery opened this issue Jun 14, 2020 · 0 comments
Open

Serialize request/response with BSON instead of JSON #11

jjavery opened this issue Jun 14, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@jjavery
Copy link
Owner

jjavery commented Jun 14, 2020

Currently request and response messages are serialized with JSON, so only types supposed by JSON can be passed between a worker pool and its workers. This prevents, for example, a Date instance from being returned by a worker function.

Look into using BSON (or another faster/more capable serializer?) so more built-in types can be deserialized unmolested.

When child_process.fork() "advanced" serialization is used, errors occur. Look into why?
@jjavery jjavery added the enhancement New feature or request label Jun 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jjavery