I'm using Archive to great effect at the moment for blog posts. But I wonder if two changes could be made to Archive that would make it much more customisable;

A setting to change the default path for archive, from archive/ to something else, even if that "something else" is used for another node. For example, the archive path could be blog/archive/ which would be much more consistent for the way I (and presumably other people) use it. Maybe this setting could be on a per-node-type basis, for each enabled node-type?

The other setting would be an option to disable the use of archive/all/ as it duplicates the functionality of the page found at archive/ and also adds an additional - not always required - step to paths. For example, instead of archive/all/2011/ we would have archive/2011/ which would be much cleaner.

These two changes would help the use of Archive blend more naturally with the pages and breadcrumbs of a site. For instance, in my use of Archive for blog posts, I would have my posts at blog/ and its archive at blog/archive/ which would allow me to produce equivalent breadcrumbs that all match up nicely.

At the moment, the whole site has perfect paths and breadcrumbs except the blog archive, which is found at archive/ and archive/all and contains no breadcrumbs at all. This is inconsistent with the way the rest of the site is set up naturally using nodes.

Thank you!