Hi All,

 

I was looking into how to implement the push model, i.e. asynchronous
communication from server to client. There're two principal options
here: a) have client ping server within some interval to see if there're
changes and b) have asynchronous communication protocol setup b/w client
and server with client listening for new messages.

 

I tried the client-based approach (a) and it worked very well, but I'd
very like to see how to actually support (b) as it's more preferable
from many standpoints. Based on the ULC documentation it seems like it
should be theoretically possible provided client queue synchronization
is used properly. When approach (a) works, there's some sort of
communication context available that collects all changes on the server
side before sending them to client in one go, so I was wondering if
there was a way to use this via API, e.g. something like:

 

CommunicationContext context = ....;

 

context.executeWithinContext(

  new Runnable() {

    run() {

        // normal code here

    }

  }

)

 

If there's something like this, I could try to use this to send the
collection of changes to client via asynchronous link. This, of course,
can be setup by many other ways. Perhaps this already exists in ULC, but
I wasn't able to find it.

 

Any pointers would be much appreciated.

 

Thanks in advance,

Dimitry

 

 

Reply via email to