views:

15

answers:

0

Hello!

We are about to move a bunch of static image and JS files into an assembly rather than hosting them as stand-alone files. Having in mind that WebResource.axd is the standard way of referencing them, would it be rational to create a custom resource handler for the following reasons:

  1. GZIP content when browser supports it
  2. Permanent URLs (since WebResource.axd involves machineKey) which are a must since they may be referenced from static (or non-aspx) files.

The question is not how to do it but rather whether it is worth doing provided the above scope.

Many thanks StackOverflow!