-
December 16th, 2010, 12:43 PM
#1
We also have found a similar issue, that we have identified as a bug in the Android base libraries for specific environments.
We observed that when a socket is forcibly closed by the application while data is still being received, a syntax-related exception can be issued either to the invocation of close() or to the currently blocked invocation of read().
Your case seems to be a variant of the one we got to know.
We are implementing workarounds for these issues in the java client library, to be available upon the next release of LS.
Our online Android demo, whose resources can be found here, is based on a more recent version of the java client library and we may apply new workarounds on that library sooner.
The latter library is compatible with Server version 3.6 as long as the SendMessage support is not used and may be used as an unsupported preview of the fixed library.
-
January 10th, 2011, 03:07 PM
#2
Hi Thomas,
we've released an update to the android lib that should solve your issue.
The library is not yet officially released so that it is not available in our standard distribution package, btw you can find a copy of the new jar with the sources of our android demo located at http://www.lightstreamer.com/share/A...Demo_Basic.zip
Any feedback is appreciated.
Similar Threads
-
By spganesh in forum Client SDKs
Replies: 1
Last Post: February 10th, 2010, 10:23 AM
-
By skidrow406 in forum Client SDKs
Replies: 4
Last Post: March 11th, 2008, 05:32 PM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 06:09 AM.
Bookmarks