Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Modules are intended to handle events raised by the application before and after the request is actually processed by the handler. Handlers, on the other hand, aren't given the opportunity to subscribe to any application events and, instead, simply get their ProcessRequest method invoked in order to the "main" work of processing a specific request.</p> <p>Take a look at this documentation from Microsoft (about half way down the page in the "The request is processed by the HttpApplication pipeline" section):</p> <p><a href="http://msdn.microsoft.com/en-us/library/bb470252.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/bb470252.aspx</a></p> <p>You can see in step 15 where the handler gets its chance to execute. All of the events before and after that step are available for interception by modules, but not handlers.</p> <p>Depending on what specific features you're trying to achieve, you could use either a handler or a module to implement an upload handler. You might even end up using both.</p> <p>Something to consider might to use an upload handler that's already written.</p> <p>Here's a free and open source one:</p> <p><a href="http://www.brettle.com/neatupload" rel="noreferrer">http://www.brettle.com/neatupload</a></p> <p>Here's a commercial one:</p> <p><a href="http://krystalware.com/Products/SlickUpload/" rel="noreferrer">http://krystalware.com/Products/SlickUpload/</a></p> <p>If you look at the documentation for NeatUpload, you'll see that it requires you to configure a module.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload