[Babeldoc-devel] EntityResolvers and Babeldoc

[McDonald, B. <Bru...@ba...>]

All,

I have been looking through the tree and I have been looking at the two entity resolvers in the core/.../pipeline/stage source directory.  There is a entity resolver for in-memory caching and one for caching on the filesystem.  These are chained - the Memory resolver uses the Disk Cache.  Now here are my thoughts:

1.  We should make these bits of code more pervasive - not just limited to the DomifyPipelineStage (which is quite fragmented at the moment).
2.  There is an opportunity for code reuse between these two classes.  The resolveEntity method shows significant similarities.
3.  Can we expand this to also implement URIResolver which is what TRaX uses?  This means that we might need to standardize how the cache documents are named in the directory (it currently uses a hashcode of the System ID).  Maybe we can "sanitize" the SystemID and the URI references (for example, all /:; becomes ~) names so that we can store the files with a name that is kinda like their original name.
4.  We need to make it so that entities can be stored in the configuration directories so that long term DTDs, Schemas can be cached in the configuration dirs.

What are your thoughts here?  Anyone have any experience with this?

regards,
Bruce.