💾 Archived View for rawtext.club › ~sloum › geminilist › 002274.gmi captured on 2020-10-31 at 14:26:21. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Pondering interfaces over the Gemini 1x responses (was: CGI)

mbays at sdf.org mbays at sdf.org

Sun Jul 19 16:50:43 BST 2020

- - - - - - - - - - - - - - - - - - -

Sunday, 2020-07-19 at 16:01 +0200 - Solderpunk <solderpunk at posteo.net>:

To my mind this is the canonical way of getting multi-part input: use

client certificates to establish a persistent session and then just

have the server send successive responses with status code 10.

In an UI like AV-98, this approach works exceptionally well and provides

a look and feel that's almost indistinguishable from using a shell

Except* that you can only have one line of output between each line of input, because 10 doesn't allow a body. This is rather limiting.

Other than adding a new response code, the nicest way I see around this is a convention that clients should make it easy to rerequest the last URI with a new query parameter. This could be done for example with a user-enabled "REPL mode" in which the client repeatedly accepts a line of input from the user and uses it as a query parameter in a new request based on the current URI.-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 195 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200719/343029d9/attachment.sig>