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.

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

2023-1-12 Meeting #43

Closed
jasnell opened this issue Jan 12, 2023 · 7 comments
Closed

2023-1-12 Meeting #43

jasnell opened this issue Jan 12, 2023 · 7 comments

Comments

@jasnell
Copy link
Contributor

jasnell commented Jan 12, 2023

  • Updates on current initiatives
    • fetch spec
    • runtime keys
    • common minimum api
    • async context
  • Identify ideal meeting time for Asia participants
@andreubotella
Copy link
Member

andreubotella commented Jan 12, 2023

  • Some talk about Igalia's involvement in WinterCG: helping proposals get off the ground, prioritization, etc.

@jasnell jasnell changed the title 2012-1-12 Meeting 2023-1-12 Meeting Jan 12, 2023
@jasnell
Copy link
Contributor Author

jasnell commented Jan 12, 2023

Meeting notes

Meeting times

Next meetings:
08:00am GMT
00:00am GMT

Fetch spec

Ethan will finish up fetch-standard administrative work on the repo to set up the next steps for fetch
Fetch specific call every other week during normal meeting spot
Should we also set up a separate fetch matrix channel, Daniel will create the room.

Runtime keys

Merged the draft spec
Tangented into a conversation about possible use of keys as module specifier prefixes
Specifiers may need to be standardized
Use of runtime keys in shared Symbol namespace

Moving forward, priorities, Igalia wants to help...

Logging, Async Context, Serverless functions...

JS: Need more effort put into surveying differences between the various capabilities platform to platform
JS: Start with a problem statement description, with requirements, and survey
DE: Is logging something that we want to tackle?
JS: We're definitely interested in logging
LC: Tying logging to async context is very interesting to deno
CW: Really need async context in deno, would be great to have standardization around this.

"Small"(ish) Work Items for quick wins:

  • WebCrypto
    • Streams
    • other web crypto fixes
  • fetch
    • getSetCookie for Headers
    • Duplex in fetch Request
  • Stream related
    • ReadableStream.from
    • TransformStream transform cancelation
    • ReadableStreams tee backpressure change
  • AbortSignal.any
  • URLPatternList
  • Socket API needs standardization. How does it relate to raw sockets

@phoddie
Copy link

phoddie commented Jan 12, 2023

@jasnell – Would you post a link to the "Socket API" and "raw sockets" APIs referenced above? I'd like to understand that landscape better. Thanks.

@jasnell
Copy link
Contributor Author

jasnell commented Jan 12, 2023

@jasnell
Copy link
Contributor Author

jasnell commented Jan 12, 2023

We don't yet have a spec for the socket api but implementation details can be found here: https://github.com/cloudflare/workerd/blob/main/src/workerd/api/sockets.h (look for the Socket class)

This, I believe, is the current wicg proposal from chrome: https://wicg.github.io/direct-sockets/ ... ours takes a slightly different (more abstracted) approach.

@ytxmobile98
Copy link

ytxmobile98 commented Jan 13, 2023

Meeting recording: https://us06web.zoom.us/rec/share/HWjvGUxIi1tHdr93BXLKlFUKPJSbMT5lyuVhjny3wESDNIyVADSf4p0CWZir6AQo.bBFEh2f0bxgwRDbR?startTime=1673539197000 Passcode: h7s_Z_FV

@jasnell

Wrong password unfortunately :(

I tried h7sZFV and h7s_Z_FV. None of them works.

@jridgewell
Copy link

jridgewell commented Jan 26, 2023

@ytxmobile98: The password is h7s*Z*FV

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants