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]/
Database Update Acknowledgement Messages
- Previous message (by thread): Database Update Acknowledgement Messages
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
Daniel.Karrenberg at ripe.net
Wed Feb 24 22:31:18 CET 1993
> Piet.Beertema at mcsun.EU.net writes: > > I don't like the idea of *by default* getting all or even > upto 20 (or some other limit) changed objects reported. > However, in some cases I would like to have this feature. > How about making it depend on the presence of the "ACK" > keyword in the Subject: line? OK, this sounds reasonable. I have implemented this using the string LONGACK rather than ACK which might legitimately be in the subject line. If you send us an update with the string LONGACK (in capitals) somewhere in the Subject:-line, the acknowledgements will contain a line saying Update OK: <object-name> for each update which generated no messages. The updates generating messages will return the full object and messages as before. Please let us know your experiences and suggestions. Daniel
- Previous message (by thread): Database Update Acknowledgement Messages
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]