Higher abstraction level: Application #13
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Chewing_Bever/lnm#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Hostheader, 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.