RE: LW as a web app
"Adam Weaver (as adam at cleversure dot com dot au)" <[email protected]>
| Newsgroups | gmane.lisp.lispworks.general |
|---|---|
| Message-ID | <SY5P282MB46384A27975AFD8F5604C8BC9C63A@SY5P282MB4638.AUSP282.PROD.OUTLOOK.COM> |
On 11 Feb 2026, at 08:23, Adam Weaver wrote: >> Does anyone else use LW for web middleware? >> I'm currently using a DELIVERed LW app to run a web service. Originally I >> wrote a HTTP/1.1 server, but then realised that I didn't want to learn >> HTTP/2 or HTTP/3. So I transitioned the front end to Caddy, and >> reverse-proxied back to my lisp code. > I am not 100% what you are trying to achieve That's because you stopped reading early. > but the way one uses runtimes in the context of webdevelopment is by reverse proxying the > request from the outside world via nginx (or any other specialised > web server) [snip pointless stuff which didn't bother to read the actual question] Damn, son, it's almost like you read the original message! But you didn't. I would've thought my use of the term "reverse-proxying back to my lisp code" might've given the hint that I'm... you know ... using a reverse proxy back to a web server. Yes, that is *exactly* what I'm doing. Caddy is a web server written in GO. It's a lot nicer to use than NGINX, and handles SSL automatically via letsencrypt without me having to faff around supplying certificates. I *could* be reverse proxying with NGINX, but I'm using Caddy instead. Same difference. Me is lisp grug. Me no care about nginx or caddy grugs. [snip description of what I described in the original message] > Fast cgi is not needed here, it is an ancient technology Bahahaha! You know we're talking about LISP, yeah? Bit cheeky referring to anything newer than 1960 as "ancient technology" 😊 >from the time when people weren’t quite sure how web development should work and the approach >described above is the standard practice nowadays. So tell me what's the difference between a fastcgi responder and a small HTTP/1.1 server, again? Apart from ephemera like how headers are parsed? I still have to spit back a HTTP.1/1 response either way. _______________________________________________ Lisp Hug - the mailing list for LispWorks users [email protected] http://www.lispworks.com/support/lisp-hug.html