# Node.js Foundation Web Server Team Meeting 2020-10-15 #72

## Agenda

Extracted from **web-server-frameworks-agenda** labelled issues and pull requests from **nodejs/web-server-frameworks** prior to the meeting.

* URL's on incoming requests [#71](https://github.com/nodejs/web-server-frameworks/issues/71)
* discuss the future of HTTP client and Undici [#66](https://github.com/nodejs/web-server-frameworks/issues/66)
* Future of HTTP High Level API Design [#60](https://github.com/nodejs/web-server-frameworks/issues/60)
* Future of HTTP Technical Plan [#55](https://github.com/nodejs/web-server-frameworks/issues/55)
* Future of HTTP Organization Plan [#54](https://github.com/nodejs/web-server-frameworks/issues/54)

## Attendance

@nodejs/web-server-frameworks

- Wes Todd (@wesleytodd)
- Michael Dawson (@mhdawson)
- Jean Burellier (@sheplu)
- Ethan Arrowood (@Ethan-Arrowood)

## Notes

- URL's on incoming requests #71
- Is fixing the perf possible?
- Could the changes be pushed into the old url api?
- Make the url creation pluggable (passed to the server when creating it)

- discuss the future of HTTP client and Undici #66
- skipped for this week

- Future of HTTP Organization Plan #54
- Not too much to talk about, we can likely take of
the agenda for a while

- Future of HTTP Technical Plan #55
- Ethan, how do we get started writing some of the
code to make forward progress on this
- Wes happy with what Robert had outlined in #60
maybe we can start with that and begin filling
things in
- Start by pusing code samples to the
web-server-frameworks repo
- Namespace it, can push whatever you want under
your username?
- Then pull common features into common section