Higher abstraction level: Application #13

New Issue

Jef Roosens · 2024-03-14T15:02:44+01:00

Jef Roosens commented

2024-03-14 15:02:44 +01:00

For my specific usecases, I would like to combine multiple separate LNM-based applications into a single event loop, served by the same process. This lowers resource requirements by letting the services share an event loop.

To achieve this, I'd like to introduce the concept of an "application", a fully self-contained LNM program. One or more of these applications can then be scheduled on the same event loop/HTTP loop, sharing resources as needed.

HTTP requests would be routed to the correct application by inspecting the Host header, the same way a reverse proxy would. Implementing this would also bring us one step closer to being able to deploy an LNM-based server as a completely standalone server, without any help from a reverse proxy for handling TLS or separating requests.

For my specific usecases, I would like to combine multiple separate LNM-based applications into a single event loop, served by the same process. This lowers resource requirements by letting the services share an event loop. To achieve this, I'd like to introduce the concept of an "application", a fully self-contained LNM program. One or more of these applications can then be scheduled on the same event loop/HTTP loop, sharing resources as needed. HTTP requests would be routed to the correct application by inspecting the `Host` header, the same way a reverse proxy would. Implementing this would also bring us one step closer to being able to deploy an LNM-based server as a completely standalone server, without any help from a reverse proxy for handling TLS or separating requests.

Jef Roosens added the

enhancement

label 2024-03-14 15:02:44 +01:00

Sign in to join this conversation.