jsr372-experts@javaserverfaces-spec-public.java.net

[jsr372-experts] WebSocket Push Component

From: Edward Burns <edward.burns_at_oracle.com>
Date: Wed, 25 Feb 2015 14:00:13 -0800

On Tuesday, February 24, 2015, Josh Juneau <juneau001_at_gmail.com> wrote:

JJ> I agree that it makes sense to standardize widely used component library
JJ> features, making them part of the core. The push component that is offered
JJ> by solution such as PrimeFaces Push is very handy, and I think including an
JJ> interpretation of that functionality would be welcomed as a standard
JJ> feature of JSF.

>>>>> On Wed, 25 Feb 2015 10:53:49 +0100, arjan tijms <arjan.tijms_at_gmail.com> said:

AT> I second this, just as 2.0 introduced the AJAX groundwork, and 2.2
AT> file upload, even though that functionality was already available at
AT> the time in component libraries, I think adding basic push support
AT> would be a good idea.

Well, we know that Cagatay has his hands full with 49-JsClientId, so we
need someone else to move this forward.

I turned up this blog entry from Cagatay:
<http://blog.primefaces.org/?p=3066>. It has a link to one JSF specific
example, using ViewParam
<http://www.primefaces.org/showcase-labs/push/viewparam.jsf?data=Pushed>.

After skimming the blog entry, it seems like PrimeFaces Push depends on
Atmosphere. Is the idea to just rewrite PrimeFaces Push but depend on
WebSocket instead? Can someone please respond with a compelling usage
example?

Thanks,

Ed

-- 
| edward.burns_at_oracle.com | office: +1 407 458 0017
|  8 days til DevNexus 2015
| 18 days til JavaLand 2015
| 28 days til CONFESS 2015