07-28-2011 07:26 AM - last edited on 07-28-2011 07:27 AM
I've asked this before and the answer was... "it will be configurable", since that is nowhere in the docs, I am guessing that never panned out. Reason I am asking is that 4.5 and below devices have very limited amount of threads available to the application. After adding Webtrends SDK to the 4.5 build of the app, I am getting too many threads exceptions in certain places, modal screens not working (i.e. one thread per modal screen), etc. So, how many threads does Webtrends actually use (I assume it's at least one, but do you spin anymore)? Remember 4.5 and below OSes have at most 16 threads available per application.
I know it's wishful thinking, but could Webtrends SDK open up a call to send the cached webtrends data on our own communications thread so that the SDK itself uses 0 threads?
Solved! Go to Solution.
08-02-2011 04:07 PM
Looking into this with Webtrends.
08-09-2011 11:33 AM
The current beta uses 4 threads, and the next release (imminent) which contains a number of significant performance improvements, will use 3.
It's not configurable, and I don't expect there will be a change to allow it to use a provided thread.
08-09-2011 04:59 PM
Thanks.
Good info. Means we won't be able to use it for pre 5.0 devices.