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/[email protected]/
"changed" field should be deleted
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Fri Jun 5 16:38:20 CEST 1998
> Michael van Elst <mlelstv at xlink.net> writes: > > Hiding the changed: lines definitely breaks every system that keeps > _copies_ of the entries because it is impossible to update entries > from these copies without trashing the existing entries. I do not understand that one. It is quite possible to send an object more than once the the update process. This will result in a NOOP update as documented in http://www.ripe.net/docs/ripe-157.html#toc27. It does not clobber anything. What am I missing? > And if you make the changed: line availables optionally then those > who want to use addresses will quickly figure out how to get them. Gabor's argument was about users with no clue (or scripts) finding addresses in output returned by whois. This would be prevented. Also we can add the usage of this flag to our heuristics which detect patterns in whois queries. Daniel
- Previous message (by thread): "changed" field should be deleted
- Next message (by thread): "changed" field should be deleted
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]