rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / code / Atom feed
* Deprecate Mongrel
@ 2013-04-10  6:03 Vipul Amler
  2013-04-11  8:26 ` John
  2013-04-15  0:14 ` James Tucker
  0 siblings, 2 replies; 4+ messages in thread
From: Vipul Amler @ 2013-04-10  6:03 UTC (permalink / raw)
  To: rack-devel

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

Mongrel isn't supported anymore[1] since the past 2-4 years. 
I see Rack::Handle::Mongrel and related specs still up in rack, which also 
spew warnings.

I would like to have feedback over removal of Mongrel related handlers from 
rack as it is deprecated, 
before I send in a PR.

Thanks.


[1] https://github.com/evan/mongrel

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 948 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Deprecate Mongrel
  2013-04-10  6:03 Deprecate Mongrel Vipul Amler
@ 2013-04-11  8:26 ` John
  2013-04-15  0:14 ` James Tucker
  1 sibling, 0 replies; 4+ messages in thread
From: John @ 2013-04-11  8:26 UTC (permalink / raw)
  To: rack-devel

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]


Why deprecate something which works so well?

We're using Mongrel 1.2pre2 with Rack and we're very happy.

I mean if you have to break something due to new features, that would 
demand a lot of work to support, then yes there is a case to be made. 
Otherwise why do so?

/pagojo



-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 1004 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Deprecate Mongrel
  2013-04-10  6:03 Deprecate Mongrel Vipul Amler
  2013-04-11  8:26 ` John
@ 2013-04-15  0:14 ` James Tucker
  2013-04-15 22:26   ` John
  1 sibling, 1 reply; 4+ messages in thread
From: James Tucker @ 2013-04-15  0:14 UTC (permalink / raw)
  To: rack-devel

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]


On Apr 9, 2013, at 11:03 PM, Vipul Amler <vipulnsward@gmail.com> wrote:

> Mongrel isn't supported anymore[1] since the past 2-4 years. 
> I see Rack::Handle::Mongrel and related specs still up in rack, which also spew warnings.
> 
> I would like to have feedback over removal of Mongrel related handlers from rack as it is deprecated, 
> before I send in a PR.

This will not happen before 2.0.

> 
> Thanks.
> 
> 
> [1] https://github.com/evan/mongrel
> 
> -- 
>  
> --- 
> You received this message because you are subscribed to the Google Groups "Rack Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 2018 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Deprecate Mongrel
  2013-04-15  0:14 ` James Tucker
@ 2013-04-15 22:26   ` John
  0 siblings, 0 replies; 4+ messages in thread
From: John @ 2013-04-15 22:26 UTC (permalink / raw)
  To: rack-devel

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]



On Monday, 15 April 2013 01:14:24 UTC+1, raggi wrote:
>
>
>
> This will not happen before 2.0.
>
>
Right I see. OK
btw out of curiosity, is it just warning which is the problem or something 
more involved?

cheers

/pagojo

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 970 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-04-15 22:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-10  6:03 Deprecate Mongrel Vipul Amler
2013-04-11  8:26 ` John
2013-04-15  0:14 ` James Tucker
2013-04-15 22:26   ` John

rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/rack-devel

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 rack-devel rack-devel/ https://public-inbox.org/rack-devel \
		rack-devel@googlegroups.com
	public-inbox-index rack-devel

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.rack.devel
	nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.lang.ruby.rack.devel
	nntp://news.gmane.io/gmane.comp.lang.ruby.rack.devel
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/rack.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git