Ordering is not needed at all. Correlation ID is enough as I expect that some
requests will take more time that another and it's OK.
Anyway, thanks a lot for your inputs!
--
View this message in context:
http://cxf.547215.n5.nabble.com/SOAP-over-WebSocket-tp5742556p5745365.html
Sent from the c
I think there is a gap between mux and what you will need for doing
async request-response calls.
With mux, you can have multiple websockets layered on a single socket
connection.
With that, you can queue requests and response multiplexed over a single socket.
But this still won't give you a reques
Yes, you need some kind of correlation Id in your SOAP message (ideally in
the header part)
But, I just learned that there is already existing subprotocol extension for
websocket called MUX whose goal is to multiplex multiple ws connections over
single TCP conection. In this case we have multiplex
Hi Przemyslaw,
the http connections need no necessarily get closed after each call,
so I don't think this is a problem. But hosting an HTTP endpoint at
the client is often not possible by its own limitation or blocked by
the network infrastructure. Another disadvantage of the conventional
decoupled
I hope this small diagram is self-explanatory
http://postimg.org/image/blg7dk2o7/
On Tue, Apr 29, 2014 at 3:20 PM, Przemyslaw Bielicki wrote:
> Yes, this is what would be nice to have as a solution with two HTTP
> connections is really bad. Not only your client needs to understand HTTP
> (acts a
Hi Przemyslaw,
Andrei's blog (the one linked in his earlier reply
http://ashakirin-cxf-async.blogspot.de/) has some examples about
asynchronous soap calls over HTTP. But the limitation of this approach
is that you will need two separate HTTP connections: one from the
client to the service and the o
Yes, this is what would be nice to have as a solution with two HTTP
connections is really bad. Not only your client needs to understand HTTP
(acts as a server), but also a HTTP connection is closed after 202
response! This is huge waste of resources, especially if you have use cases
with 1000 - 300
https://github.com/pbielicki/soap-websocket-cxf
I tested soap-websocket-webapp in both Wildfly 8.0.1-SNAPSHOT and Tomcat
8.0.3 (for Tomcat you need to add extra dependency of commons-logging). You
need to start ActiveMQ on the same machine on default port 61616.
You can use soap-websocket-client
https://github.com/pbielicki/soap-websocket-cxf
I tested soap-websocket-webapp in both Wildfly 8.0.1-SNAPSHOT and Tomcat
8.0.3 (for Tomcat you need to add extra dependency of commons-logging). You
need to start ActiveMQ on the same machine on default port 61616.
You can use soap-websocket-client
Hi Aki,
Btw. what do you call asynchronous SOAP over HTTP? How do you get a response
when it's ready?
For me, HTTP is out of question as it's synchronous protocol, whatever
tricks you make after :)
My multiplex needs is a real bidirectional, full-duplex protocol.
Cheers,
Przemyslaw
--
View th
I attached the picture but mailing list swallowed it. There you go
http://s29.postimg.org/xbqcwzpzb/cxf_websocket.png
I'm finishing a POC I will share with you in the coming days.
9 kwi 2014 09:30 "Przemyslaw Bielicki" napisał(a):
> to make my question more clear I made a simplistic and simplifi
: https://cxf.apache.org/docs/ws-addressing.html.
Regards,
Andrei.
From: Przemyslaw Bielicki [mailto:pbieli...@gmail.com]
Sent: Mittwoch, 9. April 2014 09:30
To: dev@cxf.apache.org
Subject: Re: SOAP over WebSocket
to make my question more clear I made a simplistic and simplified sequence
diagram
to make my question more clear I made a simplistic and simplified sequence
diagram.
pls let me know if this is supported in CXF? it is very similar to JMS
where you can receive requests and send responses asynchronously and in any
order.
if it's not supported, is it possible to implement it with c
Hi
On 08/04/14 18:01, Aki Yoshida wrote:
Hi Przemyslaw,
I am not sure if your multiplex case needs websockets or the normal
asynchronous soap invocation over http is suitable.
Regarding the current websocket support in cxf, it is supported out of
the box in the current 3.0.0-SNAPSHOT for some sc
Hi Przemyslaw,
I am not sure if your multiplex case needs websockets or the normal
asynchronous soap invocation over http is suitable.
Regarding the current websocket support in cxf, it is supported out of
the box in the current 3.0.0-SNAPSHOT for some scenarios and this part
is documented in the
15 matches
Mail list logo
