Felix Röthenbacher wrote: [...]
IIUC the schema has to be accessible from the browser side, i.e. there is a need for a dedicated URL space, right?
At the moment the schemas are delivered by the publication sitemap, but that should rather be done by the core. This means you're right, we need a URL space for modules.
It seems that this is a general problem for modules: how to access module resources (images, etc.) from the browser side? One solution may be to reserve a URL "prefix" to modules. E.g. http://localhost:8888/module/<module_name>/<module_specific_part>
How would this be handled when a proxy is used? I'm not a proxying expert, but I guess it would be mounted into the area URL space, wouldn't it? :8888/default/authoring/ --> :80/ :8888/modules/ --> :80/modules/ In this case, we could even forward all requests to <pub>/<area>/modules/... to the corresponding module. BTW, last night I had this idea: When delivering the schemas to BXE, we could translate the fallback:// URL into an appropriate http request URL by resolving the actual source already on the server side, using a transformer. Or did I miss something? -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
