Thanks all.

Is there an alternative to my architecture diagram that is future proof
(for websocket support)? Or an easy way to proxy and convert between
websockets and a suitable transport?

Thanks
Mike


On Thu, Jun 6, 2013 at 12:16 PM, Paul Fremantle <[email protected]> wrote:

> Thanks Oleg - that was my belief as well.
>
> Paul
>
>
> On 6 June 2013 17:09, Oleg Kalnichevski <[email protected]> wrote:
>
>> I do not see how this could possibly work without a full support for the
>> web sockets protocol at the transport level.
>>
>> Oleg
>>
>>
>> Paul Fremantle <[email protected]> wrote:
>>>
>>> The class mediator won't work. I'm pretty certain we need to build
>>> WebSocket support right into the HTTP transport. Oleg can you confirm?!
>>>
>>> Paul
>>>
>>>
>>> On 6 June 2013 15:35, Mike Stoddart <[email protected]> wrote:
>>>
>>>> (I've attached a simple diagram in PDF, assuming the mailing list
>>>> supports attachments.)
>>>>
>>>> I posted a question on Stackoverflow about websocket support in WSO2.
>>>> Someone suggested using a class mediator as a go between but I don't know
>>>> if this will work as it looks like the mediator is unidirectional.
>>>>
>>>> I have a number of web services (JAX-WS, JAX-RS and WebSockets) on the
>>>> App Server. They are unsecured.
>>>>
>>>> Can I write a proxy class that runs on the ESB that accepts incoming
>>>> websocket connections and proxies sent and received messages to/from the
>>>> ESB? I want to authenticate the user at the ESB. The ESB would proxy HTTP
>>>> and WebSocket requests to the App Server.
>>>>
>>>> The API Manager would authenticate a different set of users for the
>>>> same web services on the App Server.
>>>>
>>>> Thoughts/suggestions?
>>>> Thanks as always
>>>> Mike
>>>>
>>>> _______________________________________________
>>>> Architecture mailing list
>>>> [email protected]
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> [email protected]
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>
>
>
> --
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, VP, Apache Synapse
>
> UK: +44 207 096 0336
> US: +1 646 595 7614
>
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> [email protected]
>
> wso2.com Lean Enterprise Middleware
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, retransmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to