Gemini App Developer Guide [main]
Added a link to gritty's SCGI gemlog series
[1mdiff --git a/app-guide.gmi b/app-guide.gmi[m [1mindex d673877..efe65b8 100644[m [1m--- a/app-guide.gmi[m [1m+++ b/app-guide.gmi[m [36m@@ -288,6 +288,7 @@[m [mIn Geminispace, in the absense of financial motivations, a malicious user could[m ## 6.1 Alternatives to CGI[m [m * while CGI is quite versatile, it still assumes input to arrive via environment variables and output via stdout, with each request spawning a CGI process, which can be heavy the server; this may not be optimal for all apps; see also: SCGI, FastCGI[m [32m+[m[32m=> gemini://gemini.smallweb.space/tech-gemlog/20240108-scgi-part-iii.gmi[m * a bespoke app server is not too difficult to pull off, given Gemini's simplicity; could use an off-the-shelf solution: Sean Conner's GLV (?), mozz's JetForce (?), or skyjake's GmCapsule -- this could also be considered a possible optimization in case CGI becomes a hindrance[m * Gemini proxy servers are a bit under-documented; a Gemini server can respond to any given URL (scheme, hostname, etc.); an app could be built around this, and a proxy server that fetches remote content could be built as a stateful app, too -- use of client certificates is not well-defined, though, but generally cliets activate certs based on the request URL; the proxy server would receive this certificate instead, but cannot redo the request with cert unless it possesses a copy of the same private key -- this area is open for experimentation[m * custom apps with custom URL schemes are possible, for specialized clients, but that is outside the scope of this tutorial as those cannot be called Gemini apps[m