If wicket-atmosphere already does websockets and provides long-polling as a
fallback, and wicket-websocket just does websocket, maybe Im missing the
reason for wicket-websocket (beyond it being thinner/lighter etc.).

Maybe wicket-push has a pluggable websocket provider (similar to how Wicket
itself uses jQuery) if thats really important. With that said, my
suggestion was based on my view point:  If I want push support in my app
(and why wouldn't I, it makes for some great interactive UIs...) I want it
to work - regardless of websocket and/or long polling implementations - it
would be great to know what technique was in use (from a diagnostics /
understanding standpoint, as well as being able to talk with the various IT
security groups that are leveraging such applications). If atmosphere gives
me that, then great.  If wicket-websocket provides additional
features/functionality/simplicity, then make that the default.  Beyond
being able to push server side messages to a client over websocket/long
poll, Im not sure what other features would be required.  Ive seen library
provided multiplexing on a commercial product, but thats about it. Im sure
there are more bells and whistles.

It's great that Wicket has support for this - I think it would be simpler
and more beneficial if all work was focussed on a single module, and it was
made simpler to setup/initialize (make it a self registering plugin, with
reasonable (but overridable) defaults) out of the box.

Nick


On Wed, Nov 14, 2012 at 9:38 AM, Martin Grigorov <[email protected]>wrote:

> So you basically ask to just drop wicket-native-websocket module and
> continue with wicket-atmosphere only ?
>
>
> On Wed, Nov 14, 2012 at 4:32 PM, Nick Pratt <[email protected]> wrote:
>
> > Could we combine the wicket-websocket and wicket-atmosphere projects in
> to
> > one (wicket-push).  Full browser support for websockets (and security
> > permissions thereafter from the internal IT groups) are quite a way off.
> >  Just having a single wicket-push module would be simpler to understand.
> >  If it uses atmosphere, great.  For highly responsive and interactive UIs
> > push is definitely the way to go (IMHO).  I think having a single module,
> > with development/debugging focussed on that one module would benefit
> > everyone.
> >
> > N
> >
> >
> > On Wed, Nov 14, 2012 at 2:35 AM, Martin Grigorov <[email protected]
> > >wrote:
> >
> > > Hi,
> > >
> > > I think Atmosphere provides a bit more than what Play has.
> > > Atmosphere falls back from WebSocket to Server Side events/Long
> > > polling/Streaming if any of those is not supported by the browser
> and/or
> > > server.
> > > Play (version 2.0.4 is latest at the moment) has modules for WebSocket
> or
> > > Comet but not combined or with fallback support!
> > >
> > > Wicket also has WebSocket-only module - wicket-native-websocket (
> > > http://wicketinaction.com/2012/07/wicket-6-native-websockets/). But as
> > its
> > > documentation (
> > >
> >
> https://cwiki.apache.org/confluence/display/WICKET/Wicket+Native+WebSockets
> > > )
> > > says it will work only when WebSockets are supported by both the
> browser
> > > and the server. Just like Play's WebSocket support.
> > >
> > >
> > > On Wed, Nov 14, 2012 at 8:08 AM, pkc <[email protected]> wrote:
> > >
> > > > The atmosphere support is "experimental" right?  I just migrated from
> > 1.5
> > > > to
> > > > 6.2 and used the wicket atmosphere support but I'm having issues
> where
> > > > pushes sometimes stop working.  I thought I found a way around it by
> > > > turning
> > > > on atmosphere broadcaster caching and message length checking but
> then
> > I
> > > > got
> > > > strange behavior where other open browsers would get data meant only
> > for
> > > a
> > > > single client.  I may post a bug but I don't quite understand all the
> > > > atmosphere settings.  I wish it was a clean and simple as Play 2.1
> > > > Framework
> > > > but that is a stateless framework.
> > > >
> > > >
> > > >
> > > > --
> > > > View this message in context:
> > > >
> > >
> >
> http://apache-wicket.1842946.n4.nabble.com/Wicket-6-and-wicket-push-tp4653766p4653864.html
> > > > Sent from the Users forum mailing list archive at Nabble.com.
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
> > > >
> > >
> > >
> > > --
> > > Martin Grigorov
> > > jWeekend
> > > Training, Consulting, Development
> > > http://jWeekend.com <http://jweekend.com/>
> > >
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com <http://jweekend.com/>
>

Reply via email to