-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/03/14 19:21, Scott Lewis wrote:
> I'm working on a Remote Service provider based upon websockets [0]
> for ECF [1][2].   ECF implements the Remote Services/RSA
> specifications and runs on Felix, Equinox, and other OSGi
> frameworks.
> 
> We use HttpService to implement some of our providers, and I'm 
> interested in getting more technical details about the Felix
> HttpService implementation to see how we could best use it going
> forward.
> 
> I've looked at [3], but have some questions:
> 
> 1) What version of Jetty does the HttpService impl use/will use?

The latest released version uses Jetty 7.6.13.v20130916, and the trunk
version uses Jetty 8.1.14.v20131031 (latest version that is compatible
with JDK6). It is my intention to make a release of Felix HTTP based
on Jetty 8 soon, after which I'd like to migrate to Jetty 9 for all
kinds of reasons.

> 2) For support of rfc-189 (httpservice updates), what version will
>  support this rfc?  (i.e. it's 2.2.2 now...is there a schedule for
> the release of impl that supports rfc-189)?   More generally...what
>  release(s) of Felix will be supportive of the R6 specs?   Will all
> the sub-projects also support their respective R6 specs, or will
> they be released with separate schedules?

Some of the functionality in Felix HTTP is already based on RFC 189,
like the 'osgi.http.service.endpoints' property, but it still needs
some serious work to get all proposed functionality of RFC 189
implemented. That said, I've strong interest to keep working on
improving the current implementation towards RFC 189.

> 3) How does HttpService 2.2.2 depend upon Jetty?   (e.g.
> Import-Package from external bundle...internal to HttpService
> bundles?).  Is this going to stay the same moving forward?   What
> I'm getting at here is will there be a way for us to use the Jetty
> 9 websockets implementation via the R6 HttpService (since Jetty 9
> implements the websockets specification)?

In the current trunk version, the Jetty API is now exposed from the
felix.http.jetty bundle, to allow all kinds of extensions to be
written on top of the Jetty version used in Felix HTTP. This would
enable the use of websockets functionality from Jetty 9.
Note that currently there is a form of websocket-like functionality
provided by the cometd bundle. I haven't looked at it in a while, but
I believe the latest versions of cometd also work with websockets
directly...

Does this answer all of your questions?

- -- 
Met vriendelijke groeten | Kind regards

Jan Willem Janssen | Software Architect
+31 631 765 814

/My world is revolving around PulseOn and Amdatu/

Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK   Apeldoorn
+31 88 586 46 30

http://www.luminis-technologies.com
http://www.luminis.eu

KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTGYbfAAoJEKF/mP2eHDc4UKgP/0NG4AqhHaKrLczoWlF6qpcM
KvEpRkrUfCdCjc/snKq/cll96iYXEZbKbc1YOSHKeD2fsYlTwdYuGlHChLn0pkYT
dnYcd+c6Y9xoWztJYcr0HvJIiZVZcQYwawiFXfJG5cDz9PLaGB1OI4m5NcOn0erK
cXI9r50TdZA3z6UAmXrbhATxLd5SfPdQ10JKDyXbfSBf8SHAed0wvrTyH6+Yj0cm
TF7ZltW5toS6Z/1miy/HhepW2JbmsbgvuVHvYadFxyW9FfbBCT0/1vCGhCcATiUU
EV3V/AQIcOUAvSD92lpUZjXIZvChd4cPXTCf6ri0sDvDNEmGFRpsfFXh8rGzCn9i
UxRYL3CGce3eCCswAZ18UHK+6EfPJvt6GV5+R8BWD6lTOSLlIACLOdGfRtXC87aH
IN9ymparv/xCELCN+wtOUXl/DsUeOPhZfPlfW0uj7cErWJFNBX1dTf1DlX6fcPnW
xMlS6/12wXOz20D6fv4pAyhifqvO54QwpgHwnyVUUGt8hKaTOWNdaO6IhrYz/awJ
vSf45Q3FggQNJfcseqhYZZ9t4wXkbofHZWyO851b+EzGPgY+E3qKLCpyJvNO8X63
OszLjsGH89SONr9Kh9yBoC3Ps1gUTZ10ef04z29+fG1kOx5UW2T6EmQx0zlPjbXI
/tl/+SCCAlZyUTlKYi3g
=POnx
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org

Reply via email to