[Tickets #11071] Re: Splitting long content into multiple messages

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11071
------------------------------------------------------------------------------
  Ticket             | 11071
  Updated By         | thomas at trethan.net
  Summary            | Splitting long content into multiple messages
  Queue              | Synchronization
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


thomas at trethan.net (2012-03-25 10:16) wrote:

I just realized that client status responses are not handled at all  
(Command/Status.php)? We simply ignore responses like  
RESPONSE_SIZE_MISMATCH or RESPONSE_COMMAND_FAILED? Also
when sending items to the client, $_server_add/replace_count are  
simply incremented without checking the client's response. Is this the  
desired behavior? Wouldn't it be better to handle responses in  
Horde_SyncMl_Command::handleCommand() and react on problems? This way  
we could also log client side errors.