Compare this with Gopher which doesn't have any caching control
mechanism, thus if I go between two menus (or files) back-and-forth,
although their content didn't changed, they will get downloaded again
and again.
Therefore if we take into account the HTTP caching ability, Gopher
loses quite badly.
But on the bright side, I currently can see Gopher used perhaps in
embedded software as a way to implement control dashboards or obtain
debugging data. This is due to the protocols simplicity, where there
is no need for a Gopher client or server library, and one can use a
straight socket and be fully up-and-running, thus perhaps implement
something resembling a CGI solution in ten lines of Bash.
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project