If a feed isn't available, you could also simply use the HTTP Last-Modified header (and/or Etag) to check if the source file has changed. This doesn't help, though, if new editions are released as separate files, like Tischendorf: <a href="http://files.morphgnt.org/tischendorf/" target="_blank">http://files.morphgnt.org/tischendorf/</a><br>
<br>Weston<br><br><div class="gmail_quote">On Wed, Jan 13, 2010 at 6:59 AM, Gregory Hellings <span dir="ltr"><<a href="mailto:greg.hellings@gmail.com" target="_blank">greg.hellings@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If the websites have some sort of syndicated feed, like RSS or Atom or the like, it would be easy to write a basic script to pull the latest info from that. Likewise if there is regular version information in a web-accessible version of the file as well as the module's config file on the lines of SourceVersion=1.7.6 or SourceDate=1999-10-06 or something like that.<br>
<br>
If that sort of information is not available in a structured way, then tracking updates to the upstream material can become far more difficult.<br>
<br>
--Greg<div><div></div><div><br>
<br>
<br>
<br>
On Jan 13, 2010, at 7:37 AM, David Haslam <<a href="mailto:d.haslam@ukonline.co.uk" target="_blank">d.haslam@ukonline.co.uk</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Do we have any system in place to monitor for changes the websites where our<br>
module source texts from from?<br>
e.g. When the text itself has been updated.<br>
<br>
Or do we rely on ad hoc knowledge and reporting by interested volunteers?<br>
<br>
David<br>
-- <br>
View this message in context: <a href="http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013006.html" target="_blank">http://n4.nabble.com/Watching-websites-where-our-source-texts-come-from-tp1013006p1013006.html</a><br>
Sent from the SWORD Dev mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>