Re: [gopher] Updated Gopher RFC
On 5/8/12, Driedfruit <driedfruit@mindloop.net> wrote:
> The issue with CGI is that a complex user-supplied query is often
> needed to generate appropriate response.
CGI is a separate standard, even for HTTP. Several modern gopher
servers seem to implement CGI fairly well, or at least the subset of
it that's applicable to Gopher. I suppose a more fully-fledged "Gopher
Gateway Interface" could be worthwhile, but that's a whole new can of
worms.
>
> Gopher+ has this in +ASK definition. See also HTML forms that generate
> HTTP GET/POST requests.
>
> I'm seriously considering hijacking the CSO Phonebook entry for that
> matter, but I'm not sure if that's a good idea. Some very simple things
> could obviously be done with it, but posting whole blog posts or
> the like is much more problematic.
Simple user input can be handled via item type 7 queries. Awhile back
I wrote a phlogging script that handles comments that way
(gopher://sdf.org/1/users/wt/soft/my/germ) and I've seen a few other
scripts that use index server queries similarly.
You should hypothetically be able to handle more complex input with an
HTML form hooked up to a server-side script. I haven't tested this out
yet, but perhaps I could work up a proof- (or disproof-) of-concept
soon.
Alternatively, you could set up a server to accept input via email.
>
> --
> driedfruit
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: