This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] last-modified:, a succesor to changed:
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed Apr 16 08:36:50 CEST 2014
On Wed, Apr 16, 2014 at 08:05:08AM +0200, Tore Anderson wrote: > > Assessing the "freshness" of database objects can be a useful component > > in many business processes, but as it stands today the "changed:" > > attribute is severely crippled: > > > > Eleanor:~ job$ whois -h whois.ripe.net AS15562 | grep changed > > You'll want to use the "-B" option: As far as I understand there is a limit [1] to how often you can query the Whois Server before ending up with a (temporarily) ban. > > I propose that we introduce a new attribute called "last-modified" as a > > replacement for functionality offered by past implementations of > > "changed:". > > Makes sense to me. > > While we're at it, might as well add a similar "created:" for much the > same reasons. If others agree that a "created:" attribute (with similar syntax as "last-modified:") is a useful feature, it should be added. I myself don't immediately see how I would use "created:" in an operational context. Group, please comment on both "last-modified" and "created" attributes! Kind regards, Job [1] - http://www.ripe.net/data-tools/support/documentation/aup
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]