CLAVIN
CLAVIN copied to clipboard
Clavin web-service and client
Because it is hard to ship the lucene DB due to its size and memory constraints, we are deploying clavin as a web service. https://github.com/edwardcapriolo/clavin-aas I just wanted to get everyone's take on the project
what is the difference with https://github.com/Berico-Technologies/CLAVIN-rest
Le 26/11/2015 16:32, edwardcapriolo a écrit :
Because it is hard to ship the lucene DB due to its size and memory constraints, we are deploying clavin as a web service. https://github.com/edwardcapriolo/clavin-aas I just wanted to get everyone's take on the project
— Reply to this email directly or view it on GitHub https://github.com/Berico-Technologies/CLAVIN/issues/109.
FYI you may be interested in https://github.com/chrismattmann/lucene-geo-gazetteer.git - it has a REST service now recently too...
So one thing I noticed across all the projects is that it would be nice if ResolvedLocation and Geoname were more like java beans so we would not have to clone them to jackson serialize/deserialize. Techincally we should be able to get around that using this. http://www.cowtowncoder.com/blog/archives/2010/08/entry_409.html but I have not figured it out.
One minor differences is the project setup. I am also offering a client with the service https://github.com/edwardcapriolo/clavin-aas/blob/master/clavin-aas-client/src/main/java/io/teknek/clavin/ClavinAasClient.java