Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cherokee: dev

Re: [Cherokee] Cherokee 0.99.27 released

 

 

Cherokee dev RSS feed   Index | Next | Previous | View Threaded


gwolf at gwolf

Nov 5, 2009, 9:01 PM

Post #1 of 2 (40 views)
Permalink
Re: [Cherokee] Cherokee 0.99.27 released

Alvaro Lopez Ortega dijo [Thu, Nov 05, 2009 at 01:23:34PM -0600]:
> > Of course! I couldn't agree more.
> >
> > Future versions of Cherokee will work in that way, for sure. At the moment,
> > the best thing we can do is to continue improving the server, one step at a
> > time. You know, the perfect is enemy of the good.
> >
>
> Good news. Cherokee 0.99.28 will be the first version supporting the
> automatic configuration migrations. The first change-set implementing the
> feature already did it to trunk:
>
> http://svn.cherokee-project.com/changeset/3782

Álvaro, just in case you had any doubts on the matter... Every day you
gain a larger share of heaven. Just make sure there is still space
there for the rest of us! ;-)

--
Gunnar Wolf • gwolf[at]gwolf.org • (+52-55)5623-0154 / 1451-2244
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev


pubcrawler.com at gmail

Nov 5, 2009, 10:21 PM

Post #2 of 2 (38 views)
Permalink
Re: [Cherokee] Cherokee 0.99.27 released [In reply to]

The .99.28 automatic configuration migration might create some
discussions about touching people's config files.

I am on the fence as to what is best way to handle malformed config files.

I believe ignoring errors in config files so Cherokee does run and
prompting the user with visual notice at runtime in Cherokee-Admin and
in relative logs with error and way to clean it up is likely the best
route.

One of my big gripes with Apache in the past is the ability to malform
config files and thus not be able to actually run it. This applies to
a lot of open source software and I run up against it regularly.
MySQL is another culprit with easy to malform config files.

Point is, especially since 90%+ or more of users are config'ing
Cherokee through Admin GUI is that the GUI should sanity check the
config data on the way in so Cherokee can always be ran. Final layer
of handling should be in Cherokee-worker - extraneous or duplicative
config data should be ignored but noted by worker.

That's the approach I'd take if possible. Insure Cherokee can always
run and deal with exceptions gracefully.

-Paul

On Fri, Nov 6, 2009 at 12:01 AM, Gunnar Wolf <gwolf[at]gwolf.org> wrote:
> Alvaro Lopez Ortega dijo [Thu, Nov 05, 2009 at 01:23:34PM -0600]:
>> > Of course! I couldn't agree more.
>> >
>> > Future versions of Cherokee will work in that way, for sure. At the moment,
>> > the best thing we can do is to continue improving the server, one step at a
>> > time. You know, the perfect is enemy of the good.
>> >
>>
>> Good news. Cherokee 0.99.28 will be the first version supporting the
>> automatic configuration migrations. The first change-set implementing the
>> feature already did it to trunk:
>>
>> http://svn.cherokee-project.com/changeset/3782
>
> lvaro, just in case you had any doubts on the matter... Every day you
> gain a larger share of heaven. Just make sure there is still space
> there for the rest of us! ;-)
>
> --
> Gunnar Wolf gwolf[at]gwolf.org (+52-55)5623-0154 / 1451-2244
>
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Cherokee dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.