Make the vweb http server multithreaded + epoll/kqueue. Move it to net/http/server.v

[medvednikov]

No description provided.

[danieldaeschle]

http/server? not just http/web or even net/http/server? :)

[medvednikov]

Not sure what you are asking.

The server is in the vweb.v right now, it has to be moved to http/server.v, http module.

[JalonSolov]

There's already a net/http module. He was asking if you were talking about creating a new http module at the same level as net, or if the server should go under net/http/server.

[medvednikov]

Again, it has to be moved to http/server.v, http module.

I think I made it very clear.

http module doesn't have the server.

[JalonSolov]

So it will be net/http/server.v since net/http is the existing http module.

[medvednikov]

Correct.

[spytheman]

Moving it into net.http will burden all http clients with a web server implementation too.
I think it would be better in net.http.server, especially if we later have to support http2/http3 .

[danieldaeschle]

@spytheman you said the same thing we already did. Did you misspelled something?

[JalonSolov]

No... The previous discussions was to put it in net/http/server.v. @spytheman is suggesting putting it in net/http/server/server.v - extra level of directory, so that you do NOT get that code if you just want net.http module. You would have to import net.http.server separately.

[danieldaeschle]

Hmm net/web would also be an option? or net/http/web.

[medvednikov]

V's stdlib imitates Go's stdlib, which is now a standard. In Go, it's all in one module net.http. I don't see how having both client and server code for the protocol in one module can burden anything.

https://golang.org/src/net/http/

[JalonSolov]

The only effect is having unused code in the final executable. If you're just writing a client, you don't need (and will never call) the server code.

Perhaps this will be optimized out, perhaps not. Depends on the backend.

[medvednikov]

Unused functions will not be added to the final executable. @joe-conigliaro did some work on that and will wrap it up at some point soon.

[JalonSolov]

Very nice. Will it be done before backend is called, so it applies to all?

[medvednikov]

Yes.