lighty's life: mod_cml is dead, long live mod_cml

mod_cml is dead, long live mod_cml

jan — Wed, 02 Aug 2006 23:08:00 +0000

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 ?

"mod_cml is dead, long live mod_cml" by cb

Fri, 25 Aug 2006 09:28:53 +0000

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 ? :-)

"mod_cml is dead, long live mod_cml" by refactored

Thu, 10 Aug 2006 09:21:12 +0000

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?

"mod_cml is dead, long live mod_cml" by darix

Mon, 07 Aug 2006 13:45:42 +0000

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.

"mod_cml is dead, long live mod_cml" by Paul Querna

Mon, 07 Aug 2006 06:53:50 +0000

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.

"mod_cml is dead, long live mod_cml" by Jeff

Mon, 07 Aug 2006 06:45:00 +0000

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?

"mod_cml is dead, long live mod_cml" by anonymouse

Mon, 07 Aug 2006 05:34:48 +0000

mod_dynamic? mod_k00lk0c0d3 mod_fusion

"mod_cml is dead, long live mod_cml" by Dan Kubb

Fri, 04 Aug 2006 16:56:59 +0000

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.

"mod_cml is dead, long live mod_cml" by Sencer

Fri, 04 Aug 2006 16:02:30 +0000

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)? ...

"mod_cml is dead, long live mod_cml" by Andre Bogus

Fri, 04 Aug 2006 06:05:52 +0000

How about Core Manipulation (by) Lua? :-)

"mod_cml is dead, long live mod_cml" by jolly

Thu, 03 Aug 2006 23:51:15 +0000

If you want to keep cml why not: content manipulation language content meta language content management logic

"mod_cml is dead, long live mod_cml" by Lamby

Thu, 03 Aug 2006 17:33:10 +0000

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 ?