Hi Reza,
> 1 and 2) There is a generic Loader (org.apache.devicemap.client.Loader) > which takes in Readers (like an inputstream but it has an encoding: UTF8). > FileLoader then wraps this and loads files and I was planning on creating a > JarLoader which will detect and load resources from a jar. So it should > probably be organized a bit better (interface and package), but I think if > there is a new loading method, just wrap Loader, no? Why should we provide multiple loaders and try to imagine all the use cases when we could have only one way to initialise the client? The final users of our client are developers. I'm sure they can wrap whatever type of data source into an InputStream - files from the file system, files from a JAR, JCR nodes, Apache Sling resources, URLs, etc. I'm in favour of keeping things as simple as possible. WDYT? Cheers, Radu
