|
>> Commitment Control really shouldn't require persistence. How can this be Brad? Unless you assume that all updates occur within one message pair. You can't even guarantee that you'll be connecting to the same server job and therefore cannot guarantee the same AG. Since the AG is where the commitment control is "tied" how can it work? I'd love you to prove me wrong, I just don't see how the system would handle the mechanics of it. If Net.Data does it maybe it's somehow using a separate job to handle the actual data access - or else it is using some form of persistence under the hood. +--- | This is the WEB400 Mailing List! | To submit a new message, send your mail to WEB400@midrange.com. | To subscribe to this list send email to WEB400-SUB@midrange.com. | To unsubscribe from this list send email to WEB400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.