From ea8781abcbfba22dd14d34ca0cec6717708c6e62 Mon Sep 17 00:00:00 2001 From: Stephen Leitnick Date: Sun, 4 Feb 2024 17:26:18 -0500 Subject: [PATCH] Section --- docs/intellisense.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/intellisense.md b/docs/intellisense.md index 7724b8a8..8f2e2de8 100644 --- a/docs/intellisense.md +++ b/docs/intellisense.md @@ -104,6 +104,9 @@ A fair question to ask is: Why is this not the preferred setup for Knit? 1. A lot of extra custom code has to be written. 1. If you are willing to go to this length, then perhaps a custom-built framework would work better. +### Client-accessed Services +Services accessed from the client must still go through `Knit.GetService`, thus cannot benefit from this structural change. A secondary module could be used as the client-facing service module, but that would be a lot more work to maintain and handle. + ## Create-a-Knit Creating your own framework like Knit is quite easy. In this short section, we will set up a simple module loader that works similar to Knit's startup procedure. However, it will lack networking capabilities. There are plenty of third-party networking libraries that can be used. Choosing which networking library to use is out of scope for this section.