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

Richard S. Hall commented on FELIX-538:
---------------------------------------

Well, your not supposed to do so, but it is probably a good first step to make 
sure you have the necessary permissions, etc. Make sure you do a check out of 
Felix using "https:"...

As for the subproject directory, I was wondering about that too. Personally, I 
don't think we should use http/lightweight since that, to me, implies it is a 
module of the existing HTTP Service. I would probably just make it 
http.lightweight. The downside of this, though, is that it puts it in the same 
package namespace as the other HTTP Service impl and potentially under the same 
parent pom, which may not make sense since the two subprojects are independent.

Another possibility is to just come up with a name for it and use it as the 
subproject package name, e.g., httplite, which would put it in package 
org.apache.felix.httplite...or whatever.

Perhaps we can get some input from others?
                
> Create a really lightweight version of the HTTP Service
> -------------------------------------------------------
>
>                 Key: FELIX-538
>                 URL: https://issues.apache.org/jira/browse/FELIX-538
>             Project: Felix
>          Issue Type: New Feature
>          Components: HTTP Service
>            Reporter: Richard S. Hall
>            Priority: Minor
>         Attachments: Screenshot-Apache Felix Web Console - Bundles - 
> Chromium.png
>
>
> In my sandbox I have committed a very simple, multi-threaded, file-based web 
> server. The web server was designed so that it could easily be used in a 
> bundle (e.g., it can be started, stopped, and restarted) and already has an 
> Activator. It would be interesting if we could extend this with servlet 
> support and tailor it specifically for the OSGi HTTP Service specification.
> If we could do this, then we could have one "heavyweight" OSGi HTTP Service 
> implementation based on Jetty and this really lightweight version for small 
> device requirements

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to