News for hackers. Stuff that matters.
Re:Monitors.txt - lazy webapp monitoring by gojomo on Saturday November 05, 2011 @02:30PM (#3200502)
Interesting idea. The proliferation of convention-dictated top-level URLs offends the design sense of many web architects. Possible alternatives are to:

• shoehorn a pointer to a varying URL inside an existing convention-dictated place – as for example with sitemap pointers inside robots.txt files.

• let the resource live anywhere but specify its location to consuming services via some out-of-band mechanism. That is, you still have to tell any monitoring provider where your particular monitoring-spec lives, probably via its signup interface, but you can still use the same format and unmoving file with multiple providers.

Re:Monitors.txt - lazy webapp monitoring by groks on Saturday November 05, 2011 @04:06PM (#3200764)
Re:Monitors.txt - lazy webapp monitoring by eliot_sykes on Saturday November 05, 2011 @02:44PM (#3200558)
I'm keen on your idea for an out-of-band mechanism, and would be needed for the obfuscated URL idea

"For the more gung-ho, obfuscate the URL and use SSL (e.g. https://yoursite.tld/something-unguessable/monitors.txt) and tell your provider where to find your monitors.txt"

Re:Monitors.txt - lazy webapp monitoring by mseebach on Saturday November 05, 2011 @03:51PM (#3200727)
Another approach could be to support HTTP Basic auth.