delphi - In II7, what is the difference between an "Application", a "Module" and a "Handler"? -


currently, understanding follows.

  • when request received iis, transitions between several states (begin_request, execute_request_handler, end_request, etc).
  • a "module" dll (dynamic link library) extends functionality of iis @ 1 or more of request states. example, "php module" dll hooks iis @ execute_request_handler state parse , execute php scripts.

the above rather easy digest (and similar how apache provides extensions). however, not have clear understanding of "handlers", "handler mappings" , "applications".

  1. what "handler"? "handler mapping"?
  2. what difference between "module" , "handler"?
  3. what difference between "module" , "application"?

with last question, if enable isapi dll built delphi, difference between , application? can isapi dll added executable iis in 2 different ways, 1 via regular route , 1 via adding "application"?

(note: understand "application pools" used segregate executables producing dynamic content.)

edit: in iis developer guide, there small paragraph helps clarify difference between "module" , "handler", quoted below.

when planning develop iis feature, first question should ask whether feature responsible serving requests specific url/extension, or applies all/some requests based on arbitrary rules. in former case, should handler, , in latter, module.

essentially, understand both "handlers" , "modules" extensions functionality of iis, former response specific requests (e.g., php handler responds every request file name ends ".php") while latter provides decorator-like functionality (e.g., gzip compressing response body of handler). reference: http://www.iis.net/learn/develop/runtime-extensibility/developing-iis-modules-and-handlers-with-the-net-framework

my main question is, what difference between iis7 "application" , ii7 "handler"?

handlers

a handler used handle requests specific types of page extension or url. example each of many different extension types, *.asp, *.aspx, *.php , on have own handler types defined in iis 7+'s mmc handler mappings feature.

in old school iis6 parlance they'd equivalent of script maps.

for more information see:

http://www.iis.net/configreference/system.webserver/handlers

modules

modules consist of code plug request pipeline in application perform specific function upon every request. example, logging or sort of security feature isn't available out of box.

for more information see:

http://www.iis.net/configreference/system.webserver/modules

applications

an application comprised of of website code (including modules may have written) running in website. default single website have single application known root application. it's possible create additional applications inside same website have own application , session state distinct others.

for more information see:

http://www.iis.net/configreference/system.applicationhost/sites/site/application


Comments

Popular posts from this blog

Android layout hidden on keyboard show -

google app engine - 403 Forbidden POST - Flask WTForms -

c - Why would PK11_GenerateRandom() return an error -8023? -