Cache headers, etags etc and dynamic scheduling of re-fetch sounds useful. Why not start a little library?
On Sat, Jun 25, 2016, 13:51 Johann Höchtl <johann.hoec...@gmail.com> wrote: > > > Am Donnerstag, 23. Juni 2016 17:04:54 UTC+2 schrieb Shawn Milochik: >> >> What do you need it to do, specifically? Doing an http.Get on a page and >> storing and comparing the bytes or a hash is something you could write in >> under a minute. Why not just do that? >> > > Get notified when a change happens. Your approach would certainly work but > it's super-naive. Perform a Head Lookup and check the Timestamp when the > resurce was changed, ETags, etc. all come to my mind to checl before > downloading the whle resource. Or being able to specify a nesting level > upto which embeded resources will be fetched recursively to check for > change etc. > > So I think somebody else spent more time to think about that. There are > services in other languages of course but I was hoping for some sort of > getable service in Golang / package. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
