Hi Joe, On Nov 22, 2006, at 6:36 PM, Idaho Joe wrote:
I wonder how feasible it would be to simply schedule the transmission once per day at a time when the system is not likely to be used. (1am?) After all, is there any reason why the transmission has to be user initiated? (It's fine that it is, but does it require it?) I would imagine that it would be a simple task to 'cron' due to the fact that the communication layer is already abstracted from MLS as it is.
There is a discussion going on in the Church exploring that very idea.
Of course this would also relieve the poor finance clerk who has been there for 1.5+ hours after the block because he had to wait for all the settings apart, all the temple recommend interviews, and finally all the money counting to conclude, only to print out 2 reams of membership updates that came in with his finance transmission report.
The MLS team is very sympathetic to scenarios like the one you describe.
Bah, now I'm rambling... At any rate, for the concurrency issue, I simply suggest that MLS create a snapshot of the database, and put in a Read-Only mode so that when Afaria kicks off to transmit, MLS can still be used for reporting purposes. Fairly simple to implement since there is not conflict resolutions to overcome and a good middle ground for users because they can still view MLS data. To avoid the whole locked MLS being an inconvenience to users, I like the cron idea. Of course, YMMV.
Thanks for the suggestions. Ben
-- Joe _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
