Re: [gopher] Question about using Gopher for P2P file transfer instead of HTTP
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/24/2014 2:59 PM, Cameron Kaiser wrote:
> On the protocol side, there really isn't one; a request is a
> request. The server side might do something special to cache
> resources, but that's a factor of the server software.
Ah, I see. So something like that would be "implementation-specific."
That answers most of my question.
>>> I want to use gopher's directory menu system to make it easy to
>>> search for and find files very quickly as part of an automated
>>> process. since menus and search capabilties are a built-in
>>> inherent part of gopher, gopher sounded perfect for this.
> This is indeed Gopher's strength.
This is why I love gopher. The other biggest reason is gopher returns
us back to the value of a gopherspace being the content, not
presentation. I abhor flash, javascript, embedded java, all sorts of
non-free and closed systems for everyday access of basic information.
Gopher has built-in menu and search primitives, which makes most of
the glitz of web/http superfluous.
Thank you for the answer. This was very helpful of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS4tcRAAoJEDEXTUGm1DyUNz0IAKCcKV/t92mb2AtRZI4yZ9vG
hZlNniEdy+iT5cjPa4m++Q0bU3aJ9Gb4cmfj7TXs8b/emVI1KtkI6JDgWAlLeoZO
NIwhagQO44kadQFIwjCRrtjjOOvl2GNcqHTas10CAK1AL+WcQpC5UHcYdOUJtyAV
aLFn6Rm4JS4PSVUxTJfXjzQCRqZ74Poq0J1qa7FRTdZPZj/kCd9wKwxxIf7Z6SM8
ebW4dUYjwV/oaLjo9DTFsL5sIvbQbdS2E8k++Qz9KxqlR7bHNokwsMLQXobFQSSa
WkzU2VzBiAO5trPZSa7kOTk7s/YCP2/LdMJPLT1GZbZqspZ7B31NC8e2ezcLS8s=
=Pxbb
-----END PGP SIGNATURE-----
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Reply to: