Differences

This shows you the differences between two versions of the page.

--- jvx:communication:push_publish [2019/03/14 13:04]
admin
+++ jvx:communication:push_publish [2019/03/14 13:05]
admin
@@ Line 4: / Line 4: @@
 A standard JVx application requests data from the server side via [[jvx:communication:connections|Connection]]. This concept doesn't support sending messages from the server to the client side.
-In JVx we have a keep alive mechanism and this usually checks, every 30 seconds, if the connection to the server-side is still valid. This alive check can be used to send properties to the client, using [[jvx:communication:client_server_properties|connection properties]]. But this mechanism isn't the best approach for sending any kind of information to the client-side.
+In JVx we have a keep alive mechanism and this usually checks, every 30 seconds, if the connection to the server-side is still valid. This alive check can be used to send properties to the client, using [[jvx:communication:client_server_properties|connection properties]]. It's also known as server-side polling mechanism. But this mechanism isn't the best approach for sending any kind of information to the client-side.
 To solve this problem, we introduced the Callback Broker on server-side. This broker is available for any session via [[jvx:server:lco:sessioncontext|SessionContext]]. It makes it possible to send any objects to the client-side. The client-side is able to listen to so called call-back calls. A call-back call is not the same as an [[jvx:communication:async_callback|async call]]. The difference is that an async call will be triggered from the client-side and starts a new Thread on server-side, for the execution. A call-back call is triggered from the server-side and sends information to the client-side.