felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Gilmer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-538) Create a really lightweight version of the HTTP Service
Date Fri, 12 Aug 2011 01:57:27 GMT

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

Ken Gilmer commented on FELIX-538:
----------------------------------

I've reached a functional milestone where the service is able to load the default page for
the Felix Web Console.  There is much left to be done but I feel this marks a point where
I'm over the initial hump of getting the service working.

My next step will be HTTP methods PUT, POST, and DELETE.

Currently the project weighs in at 33 classes.  The compiled jar is about 84Kb.

I've also added an ant script and cloudbees hosted Jenkins automated build for anyone wishing
to take a look: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/

Javadoc: https://leafcutter.ci.cloudbees.com/job/lightweight%20http%20service/javadoc/
 

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message