Skip to first unread message
Jens Alfke
Mar 18, 2014, 5:30:39 PM3/18/14
to mobile-c...@googlegroups.com
One of the new features in iOS beta 3 is the use of WebSockets for the “changes feed” that sends change notifications from the server to the pull replication. This is more efficient than the “long-poll” mechanism that we used to use. But it’s a bunch of new code on both client and server, and there may be bugs in it.
If you’re upgrading to beta 3 and finding new problems with pull replications, you can try disabling WebSockets and see if that helps. To do so, just add a line like this after creating your pull replication:
pullRepl.customProperties = @{@"websocket": @NO};
If this makes the problem go away, please file a bug report. Actually file a bug report even if it doesn't help, but note that you tried this.
(Please don't pre-emptively disable WebSockets if you're not seeing problems! The new code needs testing, and it will be worth it to have it solid in 1.0. It's faster, uses less bandwidth, and puts less load on the server.)
—Jens
If you’re upgrading to beta 3 and finding new problems with pull replications, you can try disabling WebSockets and see if that helps. To do so, just add a line like this after creating your pull replication:
pullRepl.customProperties = @{@"websocket": @NO};
If this makes the problem go away, please file a bug report. Actually file a bug report even if it doesn't help, but note that you tried this.
(Please don't pre-emptively disable WebSockets if you're not seeing problems! The new code needs testing, and it will be worth it to have it solid in 1.0. It's faster, uses less bandwidth, and puts less load on the server.)
—Jens
Reply all
Reply to author
Forward
0 new messages