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

Open Questions presented to N+JSI collab summit #17

Closed

Fishrock123 opened this issue Oct 25, 2018 · 1 comment

Owner

Fishrock123 commented Oct 25, 2018

From my collab summit presentation (#16), here are the open questions I presented at the end:

Is this API likeable?
- It seemed to be well received at the collab summit
Do we need a buffer pooling helper?
- (Probably.)
Is it too API-pattern focused?
How to enforce single active request?
Where to start implementing in core?
Libuv pull streams?
- The libuv folks I catted with at N+JSI seemed open to it.

Fishrock123 mentioned this issue

Progress 15/11/2018 - November #19

Closed

Owner Author

Fishrock123 commented Jan 8, 2020

Ok I think these have been more or less answered at the last two collab summits.

To summarize, and based off of my updated questions from Montreal (#63)

API likability
- Good
API enforcement
- pattern with Verify is fine
implement in core?
- the streams3 adaptors are done and now someone needs to make Readable using bob underneath.
libuv?
- everyone agrees but no one has done it
content-addressability
- not required, quite complex
"writev"
- not necessary
buffer allocation hints
- not necessary

Fishrock123 closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment