I'd like to set record straight in regards to this issue. Verisign operates test registry to which we connect for .com,.net domains from Horizon environment. They have not fully implemented business rules inside of this registry, as crucial Auto-ACK of transfers is missing. Combine this with simple rule that you can try to transfer only domains that belong to another Registrar account over which we've got no control, needs to send confirmation emails, and it gets fairly dificult to fully support transfers in Horizon environment. The latest issue with emailsis most important, as you/your customers would probably not like to receive emails from Horizon - it would be too confusing.
This is not to say it's impossible to create some sort of solution. It would be complex, and there is always the question where to spend resources, and how much bang for the buck is this for all resellers. In addition, any solution would not prepare you for obfuscating business practices of certain registrars, so real life transfer may show to be increasingly more complex. Anyway, I've got proposal: As a band aid, would it suffice if I were to create 10K domains eligable for transfers, something like test-transfer-tucows0000..test-transfertucows9999? You'd have to itterate over them to find which one is still elligable for transfer, as once you issue tranfer command against such domain, that one is no good to anyone anymore... We can replenish this list from time to time. Please let me know. Zeljko Dimic OpenSRS Developer On Wed, 12 Mar 2003 [EMAIL PROTECTED] wrote: > On Wed, Mar 12, 2003 at 01:54:23AM -0800, [EMAIL PROTECTED] wrote: > > I've been watching the thread of complaints about OpenSRS lack of support > > for transfers in the test environment. One important point that is being > > overlooked is that OpenSRS doesn't operate the test registry. > > Well, OK, I didn't realise that. But, it's not the point. I'm trying > to test my code against OpenSRS, and they should provide a way for me > to do that -- if they're as bothered about testing as they seem to be. > > Compare the situation with credit card processing APIs - you're > provided with a card number that always works, and a card number that > always fails, and so on. It doesn't matter that Securetrading (for > example) don't run the clearing system; they're still able to provide > these testing facilities. It should be possible for OpenSRS to provide > a set of domains which will always produce the same results, in much > the same way. > > This isn't just a complaint about testing transfers, the same problems > apply to all transactions. I shouldn't have to be using > 'i-bet-this-dunt-exist.com', or even my current 'solution' - > my-domain-$date-$pid.com. > > > Chris. >
