From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 784 invoked from network); 22 Jan 2022 10:09:39 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 22 Jan 2022 10:09:39 -0000 Received: from sirjofri.de ([5.45.105.127]) by 4ess; Sat Jan 22 04:10:04 -0500 2022 Received: from sirjofri.de ([95.90.218.152]) by sirjofri.de; Sat Jan 22 09:50:13 +0100 2022 Date: Sat, 22 Jan 2022 08:50:12 +0000 (UTC) From: sirjofri To: Thaddeus Woskowiak <9front@9front.org> Message-ID: <6ebe6e81-852b-42a9-85df-902a2c81ebf4@sirjofri.de> In-Reply-To: References: <87wnitf95f.fsf@turtle-trading.net> <932CBE46-F704-4BCA-8753-7A60792E094F@quintile.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Correlation-ID: <6ebe6e81-852b-42a9-85df-902a2c81ebf4@sirjofri.de> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: patented advanced base browser polling engine template-oriented generator Subject: Re: [9front] SSH server? Reply-To: 9front@9front.org Precedence: bulk 21.01.2022 22:59:26 Thaddeus Woskowiak : > 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. sirjofri 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.