Search:

Yes it is the fixed version I think. It says Version 6.0 Build 1585

I think the polling thing was just a symptom of my testing. I have shaved a bit of time off the round-trip now on the server...

A third test, back with the large response again, and I only see 3ms on the server and a total round trip of 180ms. So that shoots a big hole in theory regarding the size of the response.

The...

Sorry our messages are crossing. The previous part of the log is shown below.

Streaming is supported (according to the status updates on my connector) and there is no proxy or intermediate layer. ...

Dario

Is the setting global or can it be set at an adapter level? If I use lighstreamer to replicate XHR transactions (as in the above example) I may well want to set it to zero, but for other...

Here is a second test, using the exact same code, but where the cached response is a trivial size. The round trip took 74ms, and here athe log is shown below. The time spent between the request and...

OK - so I have a request/response cycle that took 313ms from the "sendMessage()" to the "onItemUpdate()" on the listener.

The log is shown below. This seems to indicate that the request was...

I forgot to answer your question - no I am not using file://

I set the logging as instructed in lightstreamer_log_conf.xml but it made no difference whatsoever to the output from the server. The...

I have the client fix thanks. Now I will modify my logging and see what I can fathom out on the simple echo server. I guess a round trip of 150-170ms for a simple echo is not expected?

I am not...

I should also add that it woud be normal (without the caching test) for the bit that calls the RPG program to take around 250-250ms. I would therefore expect the total round trip to be about 300 at...

Hello Alessandro,

Your answer has me a bit worried that I have messed something up. I am not testing locally as such. The client is obviously running on my PC, and Lightstreamer is running on a...

I have been using a SmartDataProvider to perform a task which basically does this:

-> Subscription with one data element (field)
-> sendMessage from client
-> Message received by MetadataAdapter...