47 | | * There are no backwards compatibility issues: HTTP requests using the basic format will continue to work. |
48 | | * When providing resource files that use the extended format, a default file that uses the basic format must also be provided. This can simply be a copy of one of the extended versions. |
49 | | * Extended format resource files need to use the (lower)-(upper) convention (matters in Linux where filenames are case-sensitive). |
| 47 | There are no backwards compatibility issues: HTTP requests using the basic format will continue to work. |
| 48 | |
| 49 | When providing resource files that use the extended format, a default file that uses the basic format must also be provided. This can simply be a copy of one of the extended versions. |
| 50 | |
| 51 | Extended format resource files need to use the (lower)-(upper) convention (matters in Linux where filenames are case-sensitive). |