[gopher] Question about using Gopher for P2P file transfer instead of HTTP

[Mateusz Viste]

I don't really understand your question...

You seem to relate to the 'web seeding' capability of bittorrent. Using 
gpopher instead is not possible, since gopher doesn't support any 
'partial' retrieval, which is required to map bittorent chunks into http 
data offsets.

What is your need exactly? If it is software distribution, and you're 
wondering about putting "software packages" on Gopher, then I think you 
got it wrong: Gopher *does* require a server, just the same as http, so 
the solution would not be "server-less" anymore.

But I'm fairly sure I missed your point - could you clarify please with 
a simple example?

cheers,
Mateusz




On 01/23/2014 08:05 PM, Coyo wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In IRC and a surprisingly large number of other supposedly P2P
> applications, file transfer is negotiated with the P2P protocol, and
> then served with lighttpd and retrieved with curl.
>
> It seems like a good thing to reconsider this, and switch to gopher.
> My idea is that gopher can be used for caching and "last-mile"
> delivery while BitTorrent, or a similar swarming protocol, is used for
> content distribution. This separation of distribution and last-mile
> delivery is a compromise between repository designs with mirrors, and
> a fully distributed system such as apt-bittorrent, which may put more
> strain on international 10GigE links.
>
> The reason I'm worried about a better software repository system is
> because mirror servers are expensive, and so is paying through the
> nose for a commercial content distribution network. I can afford
> neither. So, I'm turning to serverless solutions, as I'm sure many
> after me will do as well. As hitting many bittorrent or other swarm
> files many times in succession can take time to warm up, using gopher
> as a final delivery seems like a reasonable and incredibly fast way to
> deliver software repository packages.
>
> I wonder how difficult it would be to implement a gopher server and
> gopher client? I would only need it as a command line application, and
> mostly the library behind it. Libgopher and libgopherd?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJS4Wf9AAoJEDEXTUGm1DyUwGQIAJfF3Wq1NZwC0HqIcMBflGXO
> bxyi+MnC6+F0pTjSLVnzITKQWIZ9gtIENPqdaN4KYVUCu6RHL+tOE8Nic0ZI6OsM
> a+6H6K1BEpchztUzoOn7ibHt3DNehR7yC0EaRx2GKAdCzzHZBGVc/ENqOXBu3pBc
> mfCqr4ytIdbd5LYfcocIiBUupoTTsTPsicQzXZppyRjRmjTdcpDZ2nhzUh5pwUSv
> h+cXDAWC6t+CZzXv/Dzwud7eUoTc0q3WuNMMC8WzT7kDi4SEAdxguo+ZuDpMIVDR
> d+iSCsgpRlt4blwZ6EcuOPU0o6njiz4lzIiyD6Okt77uX8uP/BOxRuWjcEkp6VE=
> =/4Pl
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>