Feature #5480: remove GServer from stdlib

• Status: Closed
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -

[rkh (Konstantin Haase)]

=begin
I propose removing the gserver library from Ruby's stdlib.

People should not use it for the following reasons:

• It has no tests at all.
• It does something completely different than it claims to do (the docs say it manages a thread pool, while in reality it creates a new thread for every incoming connection).
• It is not maintained.

For instance, Net::HTTPServer (https://github.com/postmodern/net-http-server) uses GServer for concurrency. Removing GServer and just serving one request at a time improves performance drastically.
=end

[nahi (Hiroshi Nakamura)]

Agree for removal as the reasons Konstantin listed, but we might need migration period. How others think?
Do we add deprecation warning in 1.9.3 from now? (and remove GServer at 2.0.)

NB: We should remove lib/xmlrpc/httpserver.rb which utilizes GServer. lib/xmlrpc/httpserver.rb is described as 'obsolete' in 2005 (See ChangeLog.) And this dependency is the reason why gserver.rb is included in 1.8 IIRC.

[ko1 (Koichi Sasada)]

• Category set to lib
• Assignee set to nahi (Hiroshi Nakamura)

I've forget this issue.
I assigned it to Nahi-san.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee changed from nahi (Hiroshi Nakamura) to hsbt (Hiroshi SHIBATA)

[hsbt (Hiroshi SHIBATA)]

• Status changed from Assigned to Closed
• % Done changed from 0 to 100

Applied in changeset r47187.

---

• lib/gserver.rb: removed unmaintained code.
  [ruby-core:40313][Feature #5480]
• lib/xmlrpc/httpserver.rb: ditto.

[postmodern (Hal Brodigan)]

For those that absolutely need to use GServer, it's also available on rubygems.

• https://rubygems.org/gems/gserver
• https://rubygems.org/gems/rubysl-gserver

However, GServer isn't being maintained, so users should migrate to an alternative or write their own threaded TCP server as needed.