Much easier, sure, but when Verisign goes down for whatever reason? I'm
sure there is redundancy in their equipment, but not necessarily in their
business practices. (: Anyhow, I do understand that this is a practical
measure, but if I were OpenSRS, I'd think about the long run, and its
future customers who are testing. At this point, I won't even let my
lead tech touch the test system, lest something breaks. He can test it
all when I finally have Full Access. (: I apologize if this is a horse
that's already been beaten in the past, and these opinions are purely my
own.
Cindy
On Tue, 21 Aug 2001, Joseph McDonald wrote:
>
> The OpenSRS test environment contacts Verisign's test environment for
> your tests. If you think about it, this makes sense. The alternative is
> for the OpenSRS system to internally simulate the registry, or have a
> test-harness which is has a different codebase from the production
> system (not a very good idea ;-) ). Much better to change a few
> hostnames in a conf file.
>
> regards,
> -joe
>
> Tuesday, August 21, 2001, 4:08:06 PM, you wrote:
>
> C> Maybe I overlooked something while searching the site for this info, but
> C> does anyone know how OpenSRS' test environment is related to Verisign's?
> C> I would think that those would be separate, but I am new here, and a lot
> C> of things are surprising to me. (: I was testing earlier and was having
> C> problems with the system, and was told that Verisign's test environment
> C> was down for maintenance, so I would have to wait till after they were
> C> done to continue (start over?) the testing.
> C> Just wondering,
> C> Cindy
>
>
>
>
--
"My theology, briefly, is that the universe was dictated but not
signed." (Christopher Morley)
