9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: Thaddeus Woskowiak <9front@9front.org>
Subject: Re: [9front] SSH server?
Date: Sat, 22 Jan 2022 08:50:12 +0000 (UTC)	[thread overview]
Message-ID: <6ebe6e81-852b-42a9-85df-902a2c81ebf4@sirjofri.de> (raw)
In-Reply-To: <CAG3JMtZSxUuGvArkJnrTvZ95gpovUv9+LJKdcVXn=fiWOVBoBQ@mail.gmail.com>

21.01.2022 22:59:26 Thaddeus Woskowiak <tswoskowiak@gmail.com>:

> They likely don't have drawterm on the build system or don't want it as 
> a dependency and want the build system to work out of the box.

In this case I assume it should be quite easy to find/write some http 
server which can provide POST for a rest-like interface, too. You can 
make it work with webhooks. The only issue so far I can see is 
authentication, but even rc-httpd solved that.

You can look at my gridchat-web project on github. Forget about the 
webapp, but the rc-httpd adjustments involved POST. It'd need some 
cleanup (and renaming since I called it PUT which was wrong but I didn't 
know it better). Also it was really heavy due to long polling for new 
messages, but for your use case it would be fine.

I wish tcp80 could handle auth and POST/PUT, since REST maps nicely to 
9p. In theory you can write your web services as fileservers and expose 
them via http.


PS it's theoretically also possible to use any other supported protocol 
(ftp, cifs) with a dedicated fileserver that waits for a write on a file 
and processes that, or use some kinda runq directory that's run every 
minute via cron that watches a directory for queue messages.

Or, just go plain tcp and write a simple command protocol yourself. You 
can try to wrap it in tls for security, it should work with certificates. 
Telnet could be pretty easy. I thing plan 9 has some legacy/old code for 
stuff like that.

  reply	other threads:[~2022-01-22 10:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 14:36 Benjamin Riefenstahl
2022-01-21 15:04 ` Stanley Lieber
2022-01-21 15:35   ` Benjamin Riefenstahl
2022-01-21 15:18 ` Sigrid Solveig Haflínudóttir
2022-01-22 13:28   ` Benjamin Riefenstahl
2022-01-21 16:23 ` Steve Simon
2022-01-21 21:59   ` Thaddeus Woskowiak
2022-01-22  8:50     ` sirjofri [this message]
2022-01-22 13:26   ` Benjamin Riefenstahl
2022-01-22 17:35     ` Steve Simon
2022-01-22 18:16     ` ori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ebe6e81-852b-42a9-85df-902a2c81ebf4@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --cc=9front@9front.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).