How would a "multiple operation transaction" version of transact! work?
(2014/07/11 0:20), Todd Berman wrote: > On Thursday, July 10, 2014 12:23:53 AM UTC-7, David Della Costa > wrote: >> Hi Todd, >> >> >> >>> So, for example, if you edit all 3 fields, it causes 3 saves to >>> be >> >>> sent, which isn't what I want at all. >> >> >> >> Can you go into a bit more detail about why this is the case? >> >> >> >> I can say that whatever the case may be, I would be hesitant to >> >> incorporate any logic for how the server should receive updates >> anywhere >> >> but in the tx-listen function. > > Unclear which case you are asking about. > > I don't want 3 saves to happen when 1 save can happen with all of the > information, especially because put 1, 2 and 3 are all using various > snapshots of the data (where 1 has edit 1, 2 has edit 1 and 2 and 3 > has edit 1, 2 and 3), with put 3 being the 'correct' one. However, > due to how the backend in question works, the writes are queued, > idempotent and not strictly ordered, so there are cases where put 2 > is the last one executed, which results in improper data being saved > on the backend. > > The reason that is happening right now is there are 3 om/transact > calls, thus 3 calls to tx-listen, and it is unclear to me how I can > guarantee that I don't do that w/o cooperation from the components, > since there is no 'multiple operation transaction' support in > om/transact > > If that wasn't the question you were asking, let me know! > > --Todd > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
