on 10-14-2015 3:11 PM
Hi All,
We are facing an issue with respect to Initial Sync and "Stay logged into Server" option.
After the initial sync, the client automatically logs out of the server, even though the Angel Transmit Configuration's "Stay logged into server" is checked.
Hence, the background sending is not working immediately after the initial sync.
If I do a delta transmit, then the client is connected to server and remains logged in and the background sending is working fine.
Below is the transmit configuration setting, that my application uses and its same for both Angel and AngelLite Transmit configuration.
How does the client remains connected to server, immediately after the initial transmit?
Thanks
Ela
Ela,
This is by design and unfortunately there really isn't a way to do this.
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 |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.