on 03-06-2008 12:31 PM
I was going thru slide on "Improvements in Data Distribution" for NW Mobile 7.1.
In the slide its written that:
Due to Event-Driven Architecture, Updates on same instance can be merged.
kindly explain "_Updates on same instance can be merged_"
Hi,
actually in version up to MI7.0 we get always the complete instance if there was an update in a single field. Lets say you have a syncBO top item and you do an update in that top item. Cause you do not know which field you updated, MI sends the complete TOP structure to the backend. If there was an update on the top stucture on the backend as well - the middleware raised a conflict and based on the rule backend or client won. Merge was not possible.
Ok, in 7.1 MI sends only the updated field. So if field A was updated on client and field B was updated in backend - even both belong to the same top structure, it is possible to merge that and build a new dataset with both changes.
Still you run into an issue, when the update takes place at the same field.
Hope that explains the issue.
Regards,
Oliver
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.