From: gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org
       Date: Mon Jul  4 19:33:59 2011
       Subject: Re: [gopher] PyGopherd - PYG and executable help
       
       On 07/04/2011 06:42 PM, Kim Holviala wrote:
       > On 2011-07-04 18:00, Cameron Kaiser wrote:
       > 
       >>> All inetd-compatible gopher daemons do that by design, Gophernicus and
       >>> Bucktooth included. I'm not sure if that's a good idea for a HTTP
       >>> gateway though...
       >>
       >> The difference being that you don't need to open a three-way pipe
       >> here; the
       >> data is passed on the command line to the daemon instead.
       > 
       > Hmm, that's actually not a bad idea. Need to think about this....
       > 
       > 
       > 
       > - Kim
       > 
       > 
       > _______________________________________________
       > Gopher-Project mailing list
       > Gopher-Project@lists.alioth.debian.org
       > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
       
       If the reason for the http/gopher gateway is the lack of native gopher
       support in the browser, I would think such a gateway would have to
       recive its input on port 80 and as such is a part of the httpd stack
       and not of the gopherd.
       
       -- 
       Jacob Dahl Pind | telefisk.org | fidonet 2:230/38.8
       
       _______________________________________________
       Gopher-Project mailing list
       Gopher-Project@lists.alioth.debian.org
       http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
       Thread start
 (DIR) [gopher] PyGopherd - PYG and executable help
 (DIR) Followup: Re: [gopher] PyGopherd - PYG and executable help