brad

Hi Calin, Many thanks for the quick response. To clarify, is the following correct? - Each of these four handlers is called by an independent thread - Two of more of the handlers may be executing concurrently - Each handler will only be called by a single thread at a time So the handlers need to safe with respect to any shared data structures, but don't need to be reentrant. Thanks, Brad

Hi again, Does the Service.sendNotificationToAllDevices method process the notification on the calling thread or asynchronously (i.e. does it block the calling thread until the message has been sent)? I realize the send time may be very quick, but my application has certain error scenarios where every millisecond counts. It's relatively simple for me to hand the notification task off to a background thread on my side, but I don't want to do this if the API is already doing so. Thanks, Brad

Hi, I have been using the Java API successfully for a while, but I have a few questions. Apologies if the information is available elsewhere, but I haven't really been able to find any real documentation. Which port does the API communicate to your servers through? I'll be moving my app to new machine shortly and need to configure the firewall. What is the threading model used? Specifically, for the following handlers: - DetailsRequestHandler - PageRequestHandler - CommandReceivedHandler - PageCommandReceivedHandler Are they guaranteed to be called by a single thread only or do I need to handle my own synchronization or make them safe for reentry (note that I have a single object that implements all these interfaces)? Finally, I use the android client app, and I get repeated "instance is offline" notifications on instance failure, instead of just one. I'm not sure if the notification delete function on the android app is not working, or if I'm receiving multiple notifications. I presume the latter. Is there any way to configure the API to only send a single notification? Thanks, Brad