Yes, batch.opensrs.net is the host, REMOTE_PORT is the same (55000)
Apologies for the late announcement on this, we had already delayed this
launch a couple of days to allow folks to get the client code.
batch.opensrs.net will, of course, remain active (it's always there, works
the same as the rr-n1-tor but isolated to help handle load).
Charles Daminato
TUCOWS Product Manager
chuck@tucows.com
On Wed, 20 Mar 2002, Jared Rhine wrote:
> Ken> Further, our initial release will be restricted to our batch pool,
> Ken> batch.opensrs.net. [...] batch.opensrs.net (RWI available at:
> Ken> http://batch.opensrs.net/resellers
>
> Hmm, ok.
>
> So if we're not using the RWI and instead using XML_Client for .US Landrush
> pre-registration, should REMOTE_HOST be 'batch.opensrs.net' and REMOTE_PORT
> 55000?
>
> I appreciate the hassles that a new launch must cause for the OpenSRS team,
> but this change is _awfully_ late notice. It almost would have been more
> fair to postpone the pre-registration opening a day or two. I've got to set
> up a separate installation and OpenSRS.conf to point to batch. I'm very,
> very glad I happen to have read this before I left today and have a couple
> hours to get things ready for this change; I already had everything scripted
> and ready to go.
>
> Ken> Once we are satisfied that our queuing is working as desired, we
> Ken> will open .us pre-registrations from the main pool,
> Ken> rr-n1-tor.opensrs.net, and announce the change to resellers.
>
> And will batch.opensrs.net remain active overlapping with this switchover?
> Or will we have to time our change exactly with the switchover to minimize
> downtime?
>
> -- jared@wordzoo.com
>
> War is God's way of teaching Americans geography. -Ambrose Bierce
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:06 EDT