[Syncevolution-issues] [Bug 4635] Google: MaxObjSize is not working in syncing with google
http://bugzilla.moblin.org/show_bug.cgi?id=4635
--- Comment #2 from Chen Congwu <congwu.chen(a)intel.com> 2009-07-22 19:08:40 ---
According to spec, MaxObjSize is used to tell the *receiving* side the
MaxObjSize the *sending* side can accept.
For this case, if user set MaxObjSize at client side, this means server should
not send items larger than this size to client. This should works as expected.
The difference with funambol is another issue, caused by:
If the client set MaxObjSize to A indicating I will not accept item size larger
than A; the server will also set it's MaxObjSize same as A, indicating *server*
will not accept item size larger than A either.
This behavior is not covered by the spec, I think this is not fatal.
(In reply to comment #0)
-------------------------------
Summary
-------------------------------
MaxObjSize is not working in syncing with google.
-------------------------------
Reproduce Step
-------------------------------
<1> syncevolution -c -y MaxObjSize=10 -l google google_1
<2> fill in a contact with large text information.
<3> two-way sync.
Large text information can be synced to goole. While same large text
information can not be synced to funambol after set MaxObjSize to 10 bytes.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.