Bug 43767 - unite resources.xmap and module-resources.xmap, review resource handling
Summary: unite resources.xmap and module-resources.xmap, review resource handling
Status: NEW
Alias: None
Product: Lenya
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: Trunk
Hardware: Other other
: P2 enhancement
Target Milestone: 2.0.1
Assignee: Lenya Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-01 04:14 UTC by J
Modified: 2007-11-02 13:22 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J 2007-11-01 04:14:20 UTC
both files can be merged into one, which can then be re-used in both contexts by
mounting it twice in the global-sitemap.xmap under different locations.
Comment 1 J 2007-11-02 13:22:56 UTC
we have a number of resource handlers in the global sitemap that i'm not sure we
need:

* does anyone use the "resources/shared" mechanism? i don't see how it's
generally useful, and publications can easily implement it in their own sitemaps.
* is static resource handling via the global sitemap still a good idea? or had
we better provide a utility sitemap that can be mounted by publication sitemaps
if needed?
* is the "inherited" mechanism really needed? i can see it might be interesting
to access template resources via a browser, but it brings us yet another magic
file infix (".inherited."). if it's worth keeping, let's document it really well.

my motivations for these suggestions are:

* cleaning of the global URL space
* simplification of the global sitemap (it should be self-documenting and really
obvious)
* better code reuse, elimination of duplicated code

imnsho, our sitemaps are lenya's *PRIMARY* user interface to those who deploy
it, and account for most of lenya's scary learning curve, so they should be
really really slick.