search

ngageoint / hootenanny

Hootenanny conflates multiple maps into a single seamless map.
GNU General Public License v3.0
356 stars 74 forks source link

Create stand-alone schema switcher service #938

Open sisskind opened 8 years ago

sisskind commented 8 years ago

Decouple schema switcher from Hootenanny into its own stand alone service, similar to translation server. Node.js is most likely to be used for implementation.

brianhatchl commented 8 years ago

NEWS FLASH: Schema switcher does use node translation server! ! !

sisskind commented 8 years ago

@brianhatchl so.....we already do this.

brianhatchl commented 8 years ago

I mean, it needs Hootenanny NodeJS module, so it doesn't work without hoot core and the hoot-js node bindings.

brianhatchl commented 8 years ago

but it doesn't use the hoot-services java code

sisskind commented 8 years ago

@brianhatchl right -- so the question is could we split out from hoot core to use as stand alone?

brianhatchl commented 8 years ago

that may be a question for @mattjdnv

brianhatchl commented 8 years ago

we'd need to package a true npm module for hoot that had the js bindings and the binary and the translation schemas

sisskind commented 8 years ago

which would really decouple the entire translation server, of which schema switching is a function of.

mattjdnv commented 8 years ago

I think that it already is separate from the Hoot core. The translation scripts are all JS and a while ago I remember having to sort out reading some of the "config" options instead of relying on hoot core to provide them - an issue with "require" statements.

An npm module sounds like a good idea. Like the mapnik server?

brianhatchl commented 8 years ago

well, not like the app I wrote, but like the module it uses, https://github.com/mapnik/node-mapnik