| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
sources.
"eventually" was used all over the project to express "possibly".
The reason why this happened is only apparent for German
speakers - in German, "eventuell" in fact has the meaning
of the English word "possibly".
A classical case of a "false friend"...
(http://en.wikipedia.org/wiki/False_friend)
|
|
0)" texts in log and SyncML
- moved mechanism down to localengineds
- added lastDBErrorText() to show DB-specific error string
only in case we actually have a DB-specific error code
- lastDBErrorText() could also be overridden in
DB implementations to return DB-specific error message
texts (base class returns a message showing lastDBError()
in case there isDBError(lastDBError()) is true, or
an empty string otherwise.
|
|
received
Patrick observed permature session abort because the Alert 222
loop detector counted 5 Alert 222 messages in less than 20 seconds.
There is a perfectly valid case where this could happen:
- client sends a message to the server with a very compact list of
deleted items
- server responds with several (> 5) messages that contain the
Status messages for the deletes, one by one (a bit strange,
but valid).
- soon the client has no changes left while the server is still
sending status replies, so the client starts sending Alert
222.
- After 5 alerts the session was aborted.
The fix is now to reset the 222 alert counter fOutgoingAlert222Count
whenever a essential (i.e. required) status response is received.
So as long as the server sends status, the 222 loop detector
will not trigger.
|
|
build
localengineds/superdatastore: client with superdatastore was
old code that needed fixing to compile.
(Generating maps from a superdatastore was never used so
far as we didn't have any client side superdatastores).
WARNING: client-side superdatastores are not tested at all.
(but also have no real use case)
|
|
non-unified builds
- First walktrough to replace #if(n)def SYSYNC_CLIENT with
new unilib macros IS_CLIENT, IS_SERVER which expand
to constants in client-only or server-only builds,
but query appBase for isServer() when both variants
are included.
|
|
ignore missing status for get/alert 222
The new mode can be enabled by setting PROFILEFLAG_LENIENTMODE
in the profileFlags of a client profile, or it can be enabled
for servers using the new <lenientmode> option in <remoterule>s.
|
|
libsmltk
|
