Hi, (New to the project and native access in general)

I am looking for something like the FileMonitor example to watch the resources contributing to a cached representation of an XSL transformation. Basically, each transformed result is made up of a source XML and XSL. The XSL can import other XSL files and call in other XML documents. The XML can include other XML files. (I can capture all of these files through EntityResolvers and URIResolvers.) So, for example, a transformation result may depend on a total of 10 files located in different places in the filesystem. I saw in the mail archives that there was a possible bug with multiple instances of the FileMonitor, but is now fixed/working.

Is FileMonitor 'more' than an example? In other words, what would keep it from being able to be used in a production environment? What would need to happen to make it production ready?

(In my case that would be a web server. I would like to trigger transforms on out-of-date representations at some interval.)

I would like to have a FileMonitor for each transformed result document. Say there are potentially 100s, 1000s or 10,000s of these result documents - is it reasonable usage of the FileMonitor?

Please forgive any ignorance :)