Questions on INPUT behavior

[Sean Conner]

It was thus said that the Great Michael Lazar once stated:
> 
> Here's the example that I was thinking about when I wrote this question. I have
> a gopher site that acts as a search engine for drink recipes [1]. Users can
> filter their search results based on predefined tags, or they can search by
> keyword using a gopher menu "7" query.
> 
> After adding some search filters, your path might look like this*:
> 
>     gopher://mozz.us:7003/1/search?tag=37&tag=5&image=1

  Wait a second ... I thought gopher URLs don't support the query type. 
It's not mentioned at all in RFC-4266 (and there are no updates as far as I
can see).

> And then if you submit a search to that path, it will append the "q=" param to
> the existing filters:
> 
>     gopher://mozz.us:7003/1/search?tag=37&tag=5&image=1&q=irish
> 
> I'm trying to think of how I could re-implement this type of application in
> gemini. And I can't really come up with a good solution if we assume that user
> input clears the current query params.

  Add on to the path component?  I did a very short version of that for my
guessing game:

	gemini://gemini.conman.org/hilo/

  -spc