Hi
@websockets: In MyFaces the implementation allows to reuse the same
websocket channel by multiple components. In other words addOnMessage logic
is implicit in jsf.push.init(...) (that's why we are passing the clientId
and channel / channelToken).
I only have one issue related to @FacesDataModel, that seems important.
I'll send the explanation asap.
regards,
Leonardo Uribe
2017-02-13 16:51 GMT-05:00 Bauke Scholtz <balusc_at_gmail.com>:
> Hi,
>
> Not critical for the functionality at least.
>
> Cheers, B
>
> On Mon, Feb 13, 2017, 22:44 manfred riem <manfred.riem_at_oracle.com> wrote:
>
>> Hi Bauke,
>>
>> Is it critical to have? Or can it be delayed to the next spec cycle?
>>
>>
>> Thanks!
>>
>> Kind regards,
>> Manfred Riem
>>
>> On 2/13/17, 2:41 PM, Bauke Scholtz wrote:
>>
>> Hi,
>>
>> It has been proposed in the user mailing that a
>> jsf.push.addOnMessage(channel, function) function would have been useful. I
>> couldn't disagree this. It gives the enduser the opportunity to register
>> push listeners without polluting the global scope, although the onmessage
>> attribute supports a namespaced function too.
>>
>> Cheers, B
>>
>> On Mon, Feb 13, 2017 at 10:23 PM, manfred riem <manfred.riem_at_oracle.com>
>> wrote:
>>
>> Hi all,
>>
>> As the start of the Public Draft Approval Ballot is approaching
>> (2017-02-21)
>> we have set this coming Thursday (2017-02-16 EOB PST) as the last date any
>> changes coming out of the Public Review can go in. If any changes come in
>> after this date we will look at them on a case by case basis, but we
>> cannot
>> make any guarantees.
>>
>> So if you have any remaining items that came out of the Public Review get
>> them
>> in as soon as possible.
>>
>> Thanks!
>>
>> Kind regards,
>> Manfred Riem
>>
>>
>>