Forum: Ruby-core [ruby-trunk - Feature #5480][Open] remove GServer from stdlib

Posted by Konstantin Haase (Guest)
on 2011-10-24 21:12
(Received via mailing list)
Issue #5480 has been reported by Konstantin Haase.

----------------------------------------
Feature #5480: remove GServer from stdlib
http://redmine.ruby-lang.org/issues/5480

Author: Konstantin Haase
Status: Open
Priority: Normal
Assignee:
Category:
Target version: 2.0


=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
Posted by Hiroshi Nakamura (Guest)
on 2011-10-25 08:02
(Received via mailing list)
Issue #5480 has been updated by 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.
----------------------------------------
Feature #5480: remove GServer from stdlib
http://redmine.ruby-lang.org/issues/5480

Author: Konstantin Haase
Status: Open
Priority: Normal
Assignee:
Category:
Target version: 2.0


=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
Posted by ko1 (Koichi Sasada) (Guest)
on 2013-02-26 00:36
(Received via mailing list)
Issue #5480 has been updated by ko1 (Koichi Sasada).

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

I've forget this issue.
I assigned it to Nahi-san.
----------------------------------------
Feature #5480: remove GServer from stdlib
https://bugs.ruby-lang.org/issues/5480#change-37012

Author: rkh (Konstantin Haase)
Status: Open
Priority: Normal
Assignee: nahi (Hiroshi Nakamura)
Category: lib
Target version: Next Major


=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
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.