Mailing List Archive: Cherokee: dev

Issue 470 in cherokee: Kill idle Information Sources

Index | Next | Previous | View Threaded

codesite-noreply at google

May 25, 2009, 4:40 AM

Post #1 of 9 (960 views)
Permalink

Issue 470 in cherokee: Kill idle Information Sources

Updates:
Summary: Kill idle Information Sources
Labels: Type-Enhancement Priority-Medium Component-Logic

Comment #1 on issue 470 by alobbs: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

(No comment was entered for this change.)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 3, 2009, 5:09 PM

Post #2 of 9 (759 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Updates:
Owner: alobbs

Comment #2 on issue 470 by alobbs: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

I was implementing this RFE when I realized that Cherokee should not be
doing this. Actually, the application
should die by itself if it's inactive for a while. Of course there will be
many application that will not implement
this behavior, but does not imply that Cherokee should.

In my understanding, we should provide an application wrapper. That
application would take care of killing its
child whenever it's been idle for a certain amount of time.

Anyway, I'm attaching the code I wrote. I'm not planing to apply it, it's
just for the record.

Attachments:
auto_kill_src-unfinished1.diff 6.4 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 19, 2009, 3:17 PM

Post #3 of 9 (719 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #3 on issue 470 by skarcha: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

I agree; if an instance of Cherokee is not using an application, this not
implies that
it is not being used by another instance or program.

But, on the other hand, the "switch" to turn on/off this feature, could be
used when
the webserver admin is sure that killing application is safe.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 20, 2009, 12:30 AM

Post #4 of 9 (728 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #4 on issue 470 by binb...@b2host.de: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

Sure it should be only enabled if wished ;-)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 20, 2009, 1:32 AM

Post #5 of 9 (720 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #5 on issue 470 by alobbs: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

I know you guys already know it, although it's worth remembering that we
should not
add superfluous to the server. Otherwise we'll end up with a fat, slow,
over-complex
and fail prone server. I bet we all agree on that.

Having said that, I must admit that I'm still unsure about whether or not
the web
server should do this by itself. The application wrapper still looks like
the most
clean method to me, actually.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 20, 2009, 1:48 AM

Post #6 of 9 (726 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #6 on issue 470 by tahers: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

+1 to the wrapper approach.

Cleaner.
Possibly simpler.
Independent (reusable).

Me thinks the other apporach is overcomplex and could introduce regressions.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 20, 2009, 2:53 AM

Post #7 of 9 (724 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #7 on issue 470 by skarcha: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

alobbs, tahers: Ok!, you convinced me... ;)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Nov 20, 2009, 3:29 AM

Post #8 of 9 (721 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #8 on issue 470 by binb...@b2host.de: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

wrapper is ok, if you provide one ;-)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

cherokee at googlecode

Apr 27, 2010, 5:35 AM

Post #9 of 9 (410 views)
Permalink

Re: Issue 470 in cherokee: Kill idle Information Sources [In reply to]

Comment #9 on issue 470 by michael.maier80: Kill idle Information Sources
http://code.google.com/p/cherokee/issues/detail?id=470

btw. I heard lighttpd team is currently working on something like this.
Which will
dynamically spawn information sources and autokill idle ones for lighttpd
2.0
to use it for mass virtual hosting

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads