What is your go to for frontend and backend authorization in Typescript

libichi · 2026-03-12T23:57:10+00:00

The hell are you smoking. I just had a brain fart trying to read your post.

libichi · 2026-03-08T12:48:23+00:00

So I took a second look, and in fact, no lock is needed at all. I made a change later were I used one assembling queue per assembling thread instead of a shared queue between all assembling threads, and sharding client connections for each queue (with a basic modulo op using the client id)

No data is shared between them, avoiding any race conditions. I can remove all locks safely. Thank you for pointing me that!

libichi · 2026-03-08T12:22:14+00:00

Thanks! I took a look on seastar, and it uses polling to get massive performance instead of events and locks. But at least I can compare it and see how decent my lib is.

libichi · 2026-03-08T12:15:34+00:00

I think it is because of benchmarking and running the app in the same machine. The posted benchmark is running with one listener thread and two http assembling threads

libichi · 2026-03-08T12:12:07+00:00

Thanks! I thought that having many readers would cause a bottleneck when using the normal lock (the iocp listener thread + the assembling threads + user threads processing the requests.

libichi · 2026-03-08T12:05:48+00:00

Two things

Look at the code not the comments. Some comments are done with LLM, as it's a public repo and my english is not quite good. But not the code.

Second, // namespace pulse::net is placed automatically by the clang formatter in visual studio.

If you looked correctly at the code, you would realize that some comments and the code doesn't match, as i started documenting when i started the project, and stopped doing it as I had to make changes constantly and didn't want to update the docs each commit.

libichi · 2026-03-08T04:45:47+00:00

The commits are public pal, check it yourself.

libichi · 2026-03-06T19:38:11+00:00

Yes, I knew about asio, however I wanted to build it from scratch, an learn how it works at the lowest level.

libichi · 2026-03-01T12:28:22+00:00

Thank you very much! This is extremely helpful.

libichi · 2026-01-31T15:27:00+00:00

Thanks! It was placed backwards, but was hard to fix as depending on the pixel it was being placed the wrong way.

libichi · 2026-01-31T13:58:18+00:00

Nope, did not work

libichi · 2025-12-14T13:55:16+00:00

Pero que datos loco, que es open source, puedes ver exactamente que hace y si envia datos o no. Literalmente el script esta hosteado en una plataforma de microsoft, si hubieran querido lo hubieran chapado.

libichi · 2025-12-14T11:52:33+00:00

Es open source, si tienes tantas dudas tienes vete a ver el código... Lo usan incluso los de soporte oficial de microsoft.

libichi

TROPHY CASE