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
Tue Apr 15 16:30:50 CEST 2014

Heya,

On Tue, Apr 15, 2014 at 03:20:12PM +0100, Nick Hilliard wrote:
> On 15/04/2014 14:31, Job Snijders wrote:
> > I propose that we introduce a new attribute called "last-modified" as a
> > replacement for functionality offered by past implementations of
> > "changed:".
> 
> % whois -h whois.ripe.net " --list-versions AS15562"

It is observant of you to mention one of the possible ways to assess the
object's freshness.

I see value in containing the information within the object itself, this
way the information is transferrable when exported to other systems: the
dbase dumps on the FTP server or when the information is replicated
through NRTM. 

Kind regards,

Job

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 ]