On 10/03/14 12:59, Santiago Pericas-Geertsen wrote:
>
> On Mar 10, 2014, at 6:07 AM, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>
>> Hi Bill
>> On 09/03/14 22:49, Bill Burke wrote:
>>>
>>>
>>> On 3/9/2014 6:36 PM, Sergey Beryozkin wrote:
>>>> Hi Marek,
>>>>
>>>>
>>>> On 06/03/14 17:03, Marek Potociar wrote:
>>>>> Hi Sergey,
>>>>>
>>>>> SSE would be a minor feature, it can go into a "dot" release as such.
>>>>> WebSocket already has a separate Java EE API, so I do not think we
>>>>> would be doing anything on that front.
>>>>>
>>>> Fine with me, we will do it in CXF :-).
>>>>
>>>> I share some of Bill's concerns, I don't really think SSE becomes
>>>> RESTful by the virtue of it binding itself to HTTP, but I'm keen to see
>>>> JAX-RS starting competing with other frameworks for building HTML5/JS
>>>> applications...
>>>>
>>>
>>> Angular JS + JAX-RS is a winning combo already.
>>>
>> Sure, you are right, I meant there has to be a standard way for JAX-RS applications to link to frameworks like Angular JS or other alternative good frameworks...
>
> What exactly do you mean by "linking" here? Angular JS is a client side (JS) framework. As such, Angular apps should access Web resources in a completely loosed coupled manner, i.e. without any knowledge of server-side framework details.
>
Of course I was not suggesting to create Angular JS client server
protocol, I meant a server side forward, the basic mechanism for JAX-RS
applications to make the response data available for various view
frameworks
Sergey
> -- Santiago
>
>
>
>