[Tickets #12605] Re: AS: Fix loss of PINGABLE flag

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12605
------------------------------------------------------------------------------
  Ticket             | 12605
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | AS: Fix loss of PINGABLE flag
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-08-23 15:33) wrote:

If this is indeed what some clients are doing maybe instead of  
ignoring the empty synckey in the ping request and letting it fall  
through to raising an invalid request exception, we should just mark  
the collection as having found changes so the client can issue a true  
SYNC?

Note that I'm not sure how a client will handle a PING response  
indicating changes in a collection that has not yet been synced, so  
this would require some testing.