Stefan de Konink wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Alvaro Lopez Ortega schreef:
> > This would be the best resource that this time:
> >
> >   svn://cherokee-project.com/cherokee/trunk/TODO
> 
> I hope my auth feature could make it into that list too ;)

Yes, Alvaro has already added it at the end of the list.

> I wonder something. Could you or maybe any other developer write on the
> website why Cherokee has such speed 'advantage' over other project,
> while the amount of features is still climbing?
> 
> - From a public relations point of view it could be considered a Good
> Thing(tm) to make clear what internal features make Cherokee great.

Well, right now Cherokee is very fast but it is not the fastest
webserver you can get;  as everybody can guess, it is still evolving wildly,
our aim is to improve it step by step and to keep it fast enough
even when new features will be added.

The TODO file contains lists of new macro features,
grouped by major version, that are desiderable to be implemented,
of course some of them could be shifted to higher versions
(i.e. 0.8.x instead of 0.7.x, etc.).

I have a personal TODO list that is filled with technical details
about "hot spots" that could be improved in future versions of Cherokee,
but as this TODO list is rather rough I'll keep it private for now.

>From a public relations point of view, having a white paper
about why Cherokee is great in some tasks (or is not in many others)
could certainly help many people to understand
when and how to use it in a successful way.

IMHO this kind of document could be written after 0.6.1 or even 0.6.2
are released;  Alvaro could say something more about this thing.


> I think this is definately a section that lacks in the FAQ or Learn More.

Yes, an updated FAQ section would be useful.

What about starting posting a few (new) general questions
about Cherokee ?

I guess that some people are wondering whether Cherokee could be used
in production environments.

I think that starting with 0.6.x versions
they can start to evaluate Cherokee and
to use it in test environments or in internal web sites.

I would say that after some testing 0.6.x could be used
to serve static content in heavy loaded web sites too.

Judging from the TODO list,
future 0.7.x versions could be much more interesting.

-- 
Nick Name:     A.D.F.
E-Mail:        <adefacc () tin ! it>
E-Mail-Format: Plain Text only (please); view using font Courier New
--
_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to