You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@joshua.apache.org by "Thamme Gowda (JIRA)" <ji...@apache.org> on 2016/06/02 22:05:59 UTC

[jira] [Commented] (JOSHUA-274) Use another HTTPServer other than Suns

    [ https://issues.apache.org/jira/browse/JOSHUA-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313173#comment-15313173 ] 

Thamme Gowda commented on JOSHUA-274:
-------------------------------------

Kellen, yes lets keep the translation core library as minimal as possible. +1 for pointing out the issue.

An option would be to setup submodule for this maven project to contain a Joshua REST service .
1. it will allow us to use Joshua from non-JVM languages. 
2. since the language packs/models are huge, its not good idea to use JOSHUA from command line when we are making too many calls (since loading takes plenty of time for each CLI call)

> Use another HTTPServer other than Suns
> --------------------------------------
>
>                 Key: JOSHUA-274
>                 URL: https://issues.apache.org/jira/browse/JOSHUA-274
>             Project: Joshua
>          Issue Type: Improvement
>          Components: decoders
>    Affects Versions: 6.0.5
>            Reporter: Lewis John McGibbney
>            Priority: Critical
>             Fix For: 6.1
>
>
> This issue concerns the use of the [HttpServer|https://github.com/apache/incubator-joshua/blob/master/src/joshua/decoder/JoshuaDecoder.java#L31] within JoshuaDecoder.java. 
> We should replace the com.sun.net.httpserver.HttpServer implementation and other Sun classes with ones from the Java API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)