(Migrated) Zato and WebSockets

(This message has been automatically imported from the retired mailing list)

Is there a way to send messages via Zato onto WebSocket connections or from
WebSocket connections?

The use-case would be to pass notification/event messages between web
components which might be on the same page or even in different browser
instances.

R

On 03/26/2014 06:26 PM, Riaan van den Dool wrote:

Is there a way to send messages via Zato onto WebSocket connections or from
WebSocket connections?

The use-case would be to pass notification/event messages between web
components which might be on the same page or even in different browser
instances.

Hi Riaan,

there isn’t any way to have WebSockets as of today.

I’m not really sure how much work it would entail but as of now, Zato
servers are mostly stateless, i.e. you execute a service and the
connection is gone.

With WS we would need to keep a lot more state around. Consider that we
have the load balancer and one or more servers - now an established
connection would have to land in the same place each time something is
pushed down a WS link to a Zato server.

Conversely - when you invoke a WS resource yourself from a Zato service
the connection needs to be kept around for longer. This itself doesn’t
sound difficult perhaps but now when you invoke a service whose previous
invocation has already established such a connection you expect it to be
reused.

Nothing in it sounds impossible it’s just that as of now there has been
no work towards WS - I’d definitely like to have it but unless this were
sponsored work, there isn’t really any chance this could be added for 1.2.

Not sure if this sounds helpful?

On 03/26/2014 06:26 PM, Riaan van den Dool wrote:

Is there a way to send messages via Zato onto WebSocket connections or from
WebSocket connections?

The use-case would be to pass notification/event messages between web
components which might be on the same page or even in different browser
instances.

Hi Riaan,

there isn’t any way to have WebSockets as of today.

I’m not really sure how much work it would entail but as of now, Zato
servers are mostly stateless, i.e. you execute a service and the
connection is gone.

With WS we would need to keep a lot more state around. Consider that we
have the load balancer and one or more servers - now an established
connection would have to land in the same place each time something is
pushed down a WS link to a Zato server.

Conversely - when you invoke a WS resource yourself from a Zato service
the connection needs to be kept around for longer. This itself doesn’t
sound difficult perhaps but now when you invoke a service whose previous
invocation has already established such a connection you expect it to be
reused.

Nothing in it sounds impossible it’s just that as of now there has been
no work towards WS - I’d definitely like to have it but unless this were
sponsored work, there isn’t really any chance this could be added for 1.2.

Not sure if this sounds helpful?