on 10-14-2015 7:26 AM
Hi All,
The ideal behaviour of an Agentry application is to allow background sending after the initial sync is done.
But the application that we use forces us to do a delta sync after the initial sync, for the background sending to be enabled.
Without doing a delta sync, the background sending does not get enabled and hence the data is not posted to the backend
The transmit configurations (Angel and AngelLite) in Agentry, have the "'Stay Logged into Server" checked.
Please share your thoughts on this
Thanks,
Pooja
Pooja,
The reason for that is when you do the initial sync your client does not have any definitions yet. It doesn't know about the two transmit configurations. The initial sync will download all the definitions and run your main fetches. Once that completes, from that point forward the client will have knowledge of what transmit configuration you are using. So by performing the delta sync after the initial sync it then utilizes one of the transmit configurations and can stay connected. I hope that helps explain why the second sync is needed to get into a stay connected session.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.