All:
I want to create a header component that will be used on all the pages
on my site. The header will contain 3 components some or all of which will
be displayed based on the page calling the component. In addition, two of
the three components are image maps. I'm using different images for the
image maps depending upon selections the user has made (highlighting).
I can see 3 ways of doing this and am wondering which is better. First,
I could load an application wide look-up table into memory, pass the page
name to the header component, then use the lookup table to determine which
components to show and which images to use. Second, I could create an API
for the reusable component that allows me to set flags for components to
show and images to use. Third, I could pass the header component a
dictionary containg the keys and values to use for the header for that page.
I am looking for a compremise between maintainability and performance,
with a bend towards performance. Any thoughts would be appreciated.
Kyle
