Thanks for the responses, how long does it usually take to implement a hotfix?
We have been playing around with a datasource that has autocommit and automerge set to false, but it appeared to be almost impossible to issue merge() and commit() sequences without running into problems. Are there any examples/tutorials on how to structure the code for a merge-resolve-commit cycle with auto-commit and auto-merge turned off? We found that sometimes the commit would throw an error because there were pending merges, this despite the fact that a merge was just completed. I presume this arose from a further push that arrived between the resolution of the last conflict and the commit request. Is there a way to make this operation atomic? By that I mean something like a mergeAndCommit() which resolves all merges, locks the data source, and then commits. Kornelius [email protected] wrote on 13/09/2006 02:13:27: > What is happening here is that the latency introduced by the poll is > causing the client to receive the response from its "commit" before a > previously queued pushed message to that client. By the time it > receives the pushed message, it is "stale" - i.e. the previous > version is not accurate anymore. We should be sending those queued > messages to the client before the client processes the response to > its operation. Thus the client would receive notification of the > conflict two times in this case but it would be the same conflict so > you would only have to resolve it once. > > The only workaround I can think of right now is to resolve that > second (stale) conflict using "acceptClient" without reporting it to > the user. The problem though is knowing when this is a stale > conflict versus a real new conflict. There is a timestamp in the > message which theoretically could be used to detect that but it is > pretty tricky so I'm not sure I'd recommend trying this workaround. > I am working on a fix now... once it is ready we could investigate > the possibility of turning it into a hotfix. > > Sorry for the problems and thanks for reporting this issue. > > Jeff > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > > > > > > > > > > > > ________________________________________________________________________ > This e-mail has been scanned for all viruses by Star. The > service is powered by MessageLabs. For more information on a proactive > anti-virus service working around the clock, around the globe, visit: > http://www.star.net.uk > ________________________________________________________________________ -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
