From: gopher-bounce@complete.org
       Date: Wed Feb 18 02:41:43 2009
       Subject: [gopher] Re: New Gopher server and client
       
       JumpJet Mailbox wrote:
       > The HTTP protocol has had "multiview" for years.  And the implementation has been (except in a few EU countries)... almost non-existent.  If hardly anyone is using multiview in HTTP, the possibility of anyone using multiview on Gopher is extremely unlikely.  
       >  
       > Multiview requires that the Server operator maintain the multiview offerings.  With Gopher now just a "hobbyists" protocol, it is improbable that anyone would take the time to maintain the alternative views (and if you think this is not so, just look at how often your favorite Gopher server operator currently updates their regular pages).  
       >  
       > That being said, I am NOT against multiview.  I just feel that energy would be better spent upon other areas of the Protocol that need to be implemented, revised, or shored-up first.  
       
       Hello
       
       On the contrary, multi-view is almost mandatory for HTTP!
       
       Frame-less versions, Java-less versions, Flash-less versions, image-less 
       versions, mobile versions, AJAX-less versions...
       
       Benn
       Thread start
 (DIR) [gopher] New Gopher server and client
       Thread start
 (DIR) [gopher] New Gopher server and client
 (DIR) Followup: [gopher] Re: New Gopher server and client
 (DIR) Followup: [gopher] Re: New Gopher server and client