In terms of APIs to implement, do we also have to implement http
on Node.js? We're currently not tracking that in the jco issue tracker, but I can create an issue for that if we want to?
asking out of ignorance/curiosity - if http is working on the web (serviceworker for inbound, fetch for outbound), is there any way to just run that without modification on node.js?
Not that I'm aware of; they're fundamentally different APIs
Or well, maybe fetch could actually work. But the server won't
A part of the mandate of the WinterCG initiative is to create common ground between the various JavaScript targets, and make sure they can run the same workloads
But somewhat unfortunately there is no public draft available yet for a common HTTP server interface
(I'm assuming that folks involved may have started on private drafts since it is probably the single-most important interface - but that's just me speculating)
Yoshua Wuyts said:
In terms of APIs to implement, do we also have to implement
http
on Node.js? We're currently not tracking that in the jco issue tracker, but I can create an issue for that if we want to?
I'm just going to create issues for this, and then we can tick off what we've already implemented
Yeah there are subtle implementation differences between Node.js fetch and browser fetch, but it might work as a shared implementation, I'm not sure. Best not to assume though.
Oh yeah, I guess one difference off the top of my head will be the way cookies are handled
In the browser they're persisted between sessions; in Node.js I'm pretty certain they're ephemeral
sounds good, thanks for filling me in
Last updated: Dec 23 2024 at 12:05 UTC