Exception [iOS]

[gianluca.bertani]

Hello,

calls to bind_session.txt are probably due to polling mode. The library may switch to polling mode when the network conditions require it. For example, if it cannot establish a streaming connection within the interval set into LSConnectionInfo.streamingTimeoutSecs.

If you believe this should not happen with your network and library settings, please enable the following log categories:

[LSLog enableSourceType:LOG_SRC_CLIENT];
[LSLog enableSourceType:LOG_SRC_SESSION];
[LSLog enableSourceType:LOG_SRC_STATE_MACHINE];

and send us the log at support@lightstreamer.com, together with the library version and build number, so we can investigate.
Best regards,

Gianluca

[DarioCrivelli]

Let me clarify the point with LSConnectionInfo->pollingSecs.

This parameter is usually 0.
This means that, in case of polling, a pure long polling is performed.
In this case, Lightstreamer does its best effort to send to the client all available updates;
as a consequence, any frequency limit settings, like LSExtendedTableInfo->requestedMaxFrequency, will be the only limits that will apply.

On the other hand, if you set it as nonzero, it forces a client-side pause between subsequent polls, which brings you in a synchronous polling scenario.
In this case, if the frequency of polls is lower than the LSExtendedTableInfo->requestedMaxFrequency setting of some item, it takes the precedence and lowers the update frequency seen by the application.

Note that this behavior has not changed.

[Dmitry Sazanovich]

Sent with Subject: Problems with iOS Client API version 1.4.1 build 157

[Dmitry Sazanovich]

Seems we have unsupportable server version 5.x

[Alessandro]

Lightstreamer Server 5.1 is currently still supported.
Lightstreamer iOS Client API 1.4.x requires Lightstreamer Server 6.
To use Lightstreamer Server 5.x, you need to go for iOS Client API 1.2.x.
Please see the changelog for full details: http://www.lightstreamer.com/distros...TML#ios_client

Seems we have unsupportable server version 5.x