This is like any registry and not just CIRA. The problem becomes that many resellers want to know right away if it got applied or not. If you go to a queue model at the registry (and OpenSRS is really nothing more then a pass-thru registry) then you send the change and OpenSRS says 'thanks I will look at it' but then when the change gets rejected.. now what?
Proper solution is for you to keep the local database. :) p. On Thu, 17 Jan 2002, Paul Chvostek wrote: > On Thu, Jan 17, 2002 at 01:15:20PM -0500, Ken Joy wrote: > > > > This was correct...but I add that the billing information is only going to > > be kept in the order, not in the contact info for the domain (which should > > be fine, since we currently don't really even store much of the .ca > > information; we grab it real time from CIRA)(for better or for worse :) > > Worse, I think, since it means that the slightest blip at CIRA is > consistently a full fledged .ca outage. Worse still, whenever CIRA is > down, my registrant customers think it's *my* fault. A more useful set > of error messages in the API would be handy. Something that spat back > better blame assignment. Since you guys make announcements to the Live > Reseller Update anyway, would it be that much more work to also put a > more informative status message to be sent back via the API? > > Are you also running "passthrough" for other heavy registries (.info and > .biz)? How is this stuff handled with them? > > Would it really be all that difficult to have OpenSRS changes to .ca > domains applied to a local database with simultaneous submission to a > queue for CIRA changes? It would involve a bit of programming, but > OpenSRS gives the impression of being able to handle such things. ;) > > -- > Paul Chvostek <[EMAIL PROTECTED]> > Operations / Development / Abuse / Whatever vox: +1 416 598-0000 > it.canada http://www.it.ca/ > --- Paul Andersen (InterNIC:PA137) [EMAIL PROTECTED] E-Gate Communications Inc. T: +1 (416) 447-7700x23 "The Trouble with doing anything right the first time is that nobody appreciates how difficult it was." - NANOG
