Hi guys,

  I just wanted to let you know I have committed some changes to add
  support for the priority and "Request" features we have been talking
  about this week.

  There is a new beta release in the usual place:

     http://alobbs.com/tmp/cherokee-0.4.29b4.tar.gz

  I have also added new examples to check that it works:

     http://svn.0x50.org/file/cherokee/qa/107-Priority1.py
     http://svn.0x50.org/file/cherokee/qa/108-Priority2.py
     http://svn.0x50.org/file/cherokee/qa/109-Priority3.py
     http://svn.0x50.org/file/cherokee/qa/110-Priority4.py

  At the end it reads the configuration file assigning a higher
  priority to each entry.  This means, your common stuff should go to
  in the beginning of the file, and then the more specific stuff.

  I would also like to clarify that the priority is between different
  types of entries (Directory, Extension or Request). Between entries
  of the same type it does not make sense. This is important.

  Let's see some examples:

===
  Directory /one/two { .. }
  Directory /one { .. }
===

  In this case the entry "/one" does NOT have a higher priority. On
  the request of "/one/two/file", it will use the configuration of the
  /one/two directory entry (and maybe inherit some property from /one
  if it is applicable).

===
  Directory /one { Handler file }
  Extension cgi { Handler cgi }
===

  On the request of "/one/file.cgi" it will execute "file.cgi" as CGI.

===
  Extension cgi { Handler cgi }
  Directory /one { Handler file }
===

  But if we swap both entries, it will send the file rather than
  execute it as CGI.


  I would love to have feedback from you guys. This is something we
  have built together :-)

--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to