mod_cml is dead, long live mod_cml 11

Posted by jan Wed, 02 Aug 2006 21:08:00 GMT

Yep, mod_cml will vanish from the distribution of lighttpd 1.5.0. It will get a new name and will get a full blown set of functions to manipulate the execution of a request in lighty.

It reason to rename mod_cml is that the focus of this module has changed from the its first implementation. It is not about checking if a request is a cache-hit or not. It is about deciding how to handle a request. Any status code can be returned, any content source will be able to be queried to assemble the content (files, memcache).

The main reason is to allow us to change the names like ‘trigger_handler’ and ‘CACHE_HIT’ to something more appropriate. In the end no big change, but a neccesary one to make the use of this powerful module more obvious. ... Perhaps the new name will be mod_cml … what would be the new meaning of this abbreviation ? Any suggestions ?

Trackbacks

Use the following link to trackback from your own site:
http://blog.lighttpd.net/articles/trackback/1897

  1. lighttpd's mod_cml will change From ThinkPHP /dev/blog
    You may have read Jo's blog entry Methods to reduce the load of your webserver by caching content: using lighttpd, MySQL UDF, LUA and speed everything up. He explained there how to use lighttpd and its mod_cml together with MySQL to provide a caching
Comments

Leave a response

  1. Lamby Thu, 03 Aug 2006 15:33:10 GMT
    I think that including the word 'cache' (or having the 'c' in mod_cml) will always confuse people into thinking its a caching system.. why not "Request Meta Language" / mod_rml ?
  2. jolly Thu, 03 Aug 2006 21:51:15 GMT
    If you want to keep cml why not: content manipulation language content meta language content management logic
  3. Andre Bogus Fri, 04 Aug 2006 04:05:52 GMT
    How about Core Manipulation (by) Lua? :-)
  4. Sencer Fri, 04 Aug 2006 14:02:30 GMT
    how about proficient hypertext processor and call it mod_php :D no wait, ... I would opt for something with "controller" because of the association that programmers/pattern-enthusiasts will make. mod_controller? mod_recon (request controller)? ...
  5. Dan Kubb Fri, 04 Aug 2006 14:56:59 GMT

    I would suggest staying away from naming the new module mod_cml if the syntax or usage is substantially different. It'll probably confuse people.

    I like Lamby's idea for mod_rml (Request Meta Language) or you could just name it something simple like mod_request.

  6. anonymouse Mon, 07 Aug 2006 03:34:48 GMT
    mod_dynamic? mod_k00lk0c0d3 mod_fusion
  7. Jeff Mon, 07 Aug 2006 04:45:00 GMT
    I think that it should be left as mod_cml because a name change would confuse and enrage me. Core Meta Language? CML Meta Language?
  8. Paul Querna Mon, 07 Aug 2006 04:53:50 GMT
    Gee, this sounds like it should be called mod_lua -- it is turning into the same kind of thing as mod_perl is to Apache HTTPD, except without all the perl slowness.
  9. darix Mon, 07 Aug 2006 11:45:42 GMT
    mod_lua would give people the impression this should be a general purpose scripting module in lighty. and the place for all the begging for mod_php/mod_per/mod_python is prepared.

    i would call for mod_logic.
  10. refactored Thu, 10 Aug 2006 07:21:12 GMT
    does this mean that in lighty 1.5.0 I'll be able to nicely handle a 404 returned from another server when using lighty as a proxy?
  11. cb Fri, 25 Aug 2006 07:28:53 GMT
    I think it resembles the concept of "edge" content/cache/servers that, for example, Akamai use. http://www.akamai.com/en/html/services/content_assembly.html http://www.akamai.com/en/resources/pdf/feature_sheets/feature_sheet_edgesuite_advcachecontrol.pdf So: mod_edge_hackwhatever ? :-)
Comments