Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Jetty Websocket Impl

Scott: https://bugs.eclipse.org/bugs/show_bug.cgi?id=401784
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Mon, Mar 3, 2014 at 12:46 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
> Hi Joakim,
>
>
> On 3/3/2014 10:18 AM, Joakim Erdfelt wrote:
>>
>> <stuff deleted>
>>
>> <stuff deleted>
>>
>> The IP / CQs for these have been taken care of already
>>
>> Client API only:
>> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=7352
>> Client + Server API:
>> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=7351
>
>
> Ok thanks.   These CQs (javax.websocket client and client+server) are for
> direct usage of javax.websocket API.  Are there any plans to put these into
> Orbit project (as bundles?)...or is the intention to distribute them
> directly from Jetty?   I'll have a look at them directly...but are they
> bundles yet?
>
>
>>
>> Note: This has confused people in the past, so I'll state it again here :)
>> javax.websocket is for the basic API, which is client side.
>> javax.websocket.server is for the server layer, which is built on-top of
>> the client API.
>> It is impossible to have a server without the client API as a result.
>> The two artifacts you see are for different roles.  One for pure clients
>> to use (such as android apps), the other is for everything else.
>
>
> Got it, thanks.
>
>> <stuff deleted>
>
>
>> Client code would only use javax.websocket API, no Jetty specifics.
>> The jetty specific implementation would be found via the
>> javax.websocket.ContainerProvider techniques.
>> http://docs.oracle.com/javaee/7/api/javax/websocket/ContainerProvider.html
>>
>> Hint: it uses ServiceLoader
>
>
> Ok, got it.
>
>> <stuff deleted>
>
>
>> We exited the release train for a number of reasons.
>> Our release schedule is more demanding than the Eclipse release cycle (and
>> it never synchs or lines up nicely for either side).
>> Our active development is on Servlet API 3.1, which means we have a
>> minimum JDK requirement of Java 7 (forcing this requirement on the rest of
>> eclipse was undesired, so we stepped out)
>> We have no OSGi or P2 developers. (we have a jetty-osgi module that is
>> unmaintained and has undergone several votes this past year for removal.)
>> The demand for OSGi this and that comes nearly exclusively from other
>> Eclipse projects, hardly ever any external projects.
>
>
> Well, yes :).   But as a fellow Eclipse RT project...and based upon
> OSGi...we need to ask about OSGi support.
>
> As ECF's project lead I understand the resource-based decisions wrt release
> train...I'm just trying to figure out how we can best use jetty's impl of
> this new standard (websockets) as opposed to using some other websockets
> impl...in order to release this new remote service provider as part of Luna.
>
>>
>>  <stuff deleted>
>>
>>
>> Can't speak for the Luna point of view, but the WebSocket API in Jetty 9.1
>> feels stable enough (so far).
>> We have a few requests for features in the API surrounding PING/PONG/FRAME
>> access, but that's rather low level and we are looking for a minimal
>> approach to allow them.
>
>
> Where can I get some definitive word WRT the Luna (Equinox+Eclipse) usage of
> Jetty (i.e. which version of jetty will be used in Luna)? Is this a RT PMC
> question?
>
>
> Thanks,
>
> Scott
>
>
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top