Hello Brian, as far as I remember this is just a key that prevents double renewals. The system will renew a domain but will not renew a second try with the same key (and also will cancel all pending orders if any with the same key). Setting it as a current expiration year is just one way to set a unique value.
Regards --- Tuesday, February 13, 2007, 6:41:51 AM, you wrote: D> Hello D> I am looking at the API specifications 2.8.1 & 2.9.6 under "Renew Domain" D> (pages 267 - 272 in 2.9.6 docs), specifically the response codes starting at D> the bottom of page 271. D> Apparently, if you pass the wrong current expiration year, you should D> receive a response 541 "Invalid attribute value" (or, possibly 555 "Domain D> already renewed"), but in the real world, it renews the domain (or pends it, D> as the case may be), and happily sends along a 200 "Command completed D> successfully", making it appear to be a bug in my code. D> It wasn't until after I spent a few hours looking for my bug that I realized D> I had done everything correct on my end (everything, that is, but pass the D> correct current expiration year), but the 541 (or 555) never came back. D> Whom should I report this to? D> Thanks D> Brian O'Donnell D> Doctor PC D> www.doctorpc.ca D> _______________________________________________ D> domains-dev mailing list D> [email protected] D> http://discuss.tucows.com/mailman/listinfo/domains-dev _______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
