At 2/6/02 12:33 PM, Daniel Manley wrote:
>notice the "elsif" that checks for response code 300 for delayed
>success. Then the final else for full success. This means no code
>changes for when .name go synchronous. Client 2.49 should be usable for
>future sync nameserver, forwarding email and (eventual) contact changes.
Ah, okay. I was actually looking at the nameserver part, not the e-mail
part, but I see that it has some similar code that looks for a response
code 250 -- is that the same thing (i.e., the server returns code 250 for
nameserver modifications during pre-reg, but will be changed to something
else when the registry is live)?
If so, you're absolutely right; I misunderstood the meaning of
"asynchronous registry" in the comments (I assumed this was a fixed
attribute of a given registry, not something that would change). My
apologies.
-- Robert L Mathews, Tiger Technologies"The trouble with doing something right the first time is that nobody appreciates how difficult it was."
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:03 EDT