On Tue, 6 Jun 2006, Tom Welch wrote:
My thoughts were to create a central repository (whether hosted by the church
or individually would be up for debate) and then we could provide several
ways to access that data.
1. We (the community) could provide a SOAP or other interface to the data so
that people could write thick client applications and synchronize their data
with the central repository. I've actually done this quite successfully with
some other applications and it works VERY well. So you can run independent
of the server but when you go "back online" you can "sync" your data. If a
person chose to never "work online" that would work fine as well.
Oh yeah, this has my vote!
Follow the CVS/SVN model. I 'checkout' a snapshot of the latest data with
my local client. I take my laptop to the committee meeting, informal meetup
with the boy/girl and their parents, or whatever, and input any updates I
find. Once I'm back online I login and 'commit' any local changes I've
made.
If a central web-app were provided by the church, who hosted the data
repository, and provided an API into the data, then parents and leaders
can use the web-app to see everyone's progress. The community could then
build various means of downloading/updating/etc that data.
The Palm/handheld crowd could have their clients, the Perl folks (woohoo!)
could make Net::LDS::ScoutTrack, and build whatever apps on top of that,
the Java folks could do their thing, as could the Python folks. And
Bishop, bless his heart, just has to login to the church's web-app to see
where everyone is at.
Sounds good to me :-).
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
