Re: Latest and hopefully last iteration of ripe-81++
- Date: Thu, 21 Jul 94 17:45:16 MET DST
- Organization: GARR Network Information Service
>
>
> Laurent Joncheray lpj@localhost writes
> * Introducing several updates a day when the 'changed'
> * attribute has a granularity of 1 day can result in inconsistancies in the
> * database when you use email for the update. More than 1 update a day
> * should be avoided in your current implementation.
> * Laurent
> *
> * PS: Yes Tony "The software allows more than one update a day":
> * - i send a update at 15:00, but i have email problems and the mail is
> * delayed 1h (common value with sendmail).
> * - i send a update at 15:20 because i realized i did a typo. The email probl
> * em
> * is gone and the mail is not delayed.
> * - The result is left as an exercise for the reader :-)
> * Actually i am wondering if 'dbupdate' check the date in the email header?
>
> You are very right, it is strange however that over the few hundreds
> of thousands up updates this has never happened. I usually wait for an
> acknowledgement before I send in a new update.
>
> And no, dbupdate does not check the date in the email header, it is as
> reliable as mail itself.
>
> These are implementation and general database matters, NOT ripe-81++
> matters. We should take implementation matters offline, and not bother
> all these mailing lists with it.
>
> -Marten
>
I agree with the argument:
"These are implementation and general database matters, NOT ripe-81++"
Personal comments like mine on the mail from Laurent should not delay
the approval of the document. Sorry if I wasn't clear enough...
---------- ----------
Antonio_Blasco Bonito E-Mail: bonito@localhost
GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito
c/o CNUCE - Istituto del CNR Tel: +39 (50) 593246
Via S. Maria, 36 Telex: 500371 CNUCE I
56126 PISA Italy Fax: +39 (50) 904052
---------- ----------
|