Re:Show HN: I wrote a gopher client and decided to put it on...
by enneff on Tuesday December 14, 2010 @05:19AM
(#2003749)
Thank you.
It's rudimentary, but it works. It demonstrates a couple of Go concepts:
- goroutines (to Serve each request)
- interfaces (the Listing type implements the path.Visitor pattern so it can generate itself, and both the Entry and Listing types implement the fmt.Stringer interface so that fmt can stringify them).
Re:Show HN: I wrote a gopher client and decided to put it on...
by davidblair on Tuesday December 14, 2010 @04:45AM
(#2003685)
In some respects HN is a Gopher server adapted for today. Focused on content, links to information, and just enough detail to keep you going.
As a protocol, Gopher is straight forward. Whenever someone talks about the "semantic web" I'm always reminded of Gopher has been doing since 1991. It is in no way perfect, but worked well.
Re:Show HN: I wrote a gopher client and decided to put it on...
by dfox on Tuesday December 14, 2010 @07:13AM
(#2003912)
I like to use gopher for early demonstrations that some low-level networking code works or how it should be used. It is certainly easier to write working gopher client/server than to deal with intricacies of HTTP or most other protocols when you want to test that TCP stack or code that breaks down incoming byte stream into lines actually works.
And I'm seriously considering writing GUI gopher client as an all-encompassing example in dfsch.
Re:Show HN: I wrote a gopher client and decided to put it on...
by beaumartinez on Tuesday December 14, 2010 @05:23AM
(#2003757)
Gopher?! Why? Also, I'm pretty sure the reason most Gopher clients were abandoned was in fact due to the explicit lack of coffee making, you might want to at least make some attempt at an implementation...
It's rudimentary, but it works. It demonstrates a couple of Go concepts:
- goroutines (to Serve each request)
- interfaces (the Listing type implements the path.Visitor pattern so it can generate itself, and both the Entry and Listing types implement the fmt.Stringer interface so that fmt can stringify them).
As a protocol, Gopher is straight forward. Whenever someone talks about the "semantic web" I'm always reminded of Gopher has been doing since 1991. It is in no way perfect, but worked well.
gopher://synack.me/
I have fond memories of spelunking around gopher servers back in 1993. :)
And I'm seriously considering writing GUI gopher client as an all-encompassing example in dfsch.