Charles, I think everyone at TUCOWS would take exception to the term "pseudo-registrar"....
If all you want to do is your own registrations, you may want to take a very hard, serious look at running the standard PERL client on your Windows box. It works just fine, and while the *nix contingent is usually the most vocal here, there are quite a few of us running Windows. I'm not exactly fluent in Perl, but we've been running here for a couple of years. It's no hassle. -- Lynn On Tue, 14 Jan 2003 15:05:09 -0600, [EMAIL PROTECTED] wrote: > >I beleive I understand the handshaking command set, but >sample can only make my task easier while imposing on you >even more. > >I beleive I have a working Blowfish Encode / Decode >function and I did see the Dev-List message which >describes the necessary Private Key "pre-hash". So I'm >hoping I now just need the actual data to transport and >parse for results. > >Bottom lines, > >1) I simply have a personal reseller account with Tucows >so my needs are extremely simplistic. I use Tucows for >thier awsome service and the convienance of being a >pseudo-registrar. > >2) I'm a "Widows person" with no available Perl or PHP >resources. I can't even exchange favors with a Linux >Buddy. ;-( > >3) I have lots of successful Windows network coding >experiance, so TCPIP coding, etc, should be a non-issue >for me. > >4) All I currently need to do (and for the forseeable >future) through automation is register new .Info domains. >If I ever need to do more then I'm betting the API can >empower me to modify a working .Info "regstration system". > >5) So I would like the most simplistic and sterile sample >message(s) / conversation needed to register a new .Info >domain via the OpenSRS API. > >THANK YOU VERY MUCH for your help! > >I really do appreciate any and all help you have time to >provide me with. > >Charles > > >On Tue, 14 Jan 2003 11:35:03 -0500 >Colin Viebrock <XXXXX> wrote: > >Are you just looking for the .INFO reg command, XML-ized? >Or do you >need the entire handshaking command set too? > >Appendix A of the API docs is helpful in figuring out the >XML format, >and Appendix C explains the handshaking process.* > >- Colin > >* NOTE: Section 11.2 of the API specification is no longer >valid, and >should be ignored. Maybe Chuck can get someone at OpenSRS >to take that >out of the spec. > > > > > >XXXXX wrote: > >Tucows support suggested I join this list and ask the >following: > >Can anyone *PLEASE* provide me a sample new (not renew or >transfer) .INFO domain registration request packet (non >encrypted of course) which gets sent to OpenSRS server, >and it's response packet (both success and failure). > >Specifically the unencrypted version of the TCPIP packet >data that gets sent to the port 55000 server. I can then >us this as my template to perform the registration process >using my own code and reseller ID information (obviously >your ID information is blank out if the sample packet). > >Bottom line is that I have read though the OpenSRS API >document and, like many such documents, it assumes you >know what you are doing before you've ever done it -- Thus >it's just a referance document. Simply put this document >would be much more useful if it tied the document together >with 1 or 2 *COMPLETE* send / receive examples. Perhaps >for something that every reseller is likely to do, like >register a new domain name .... Ok, I feel better now. ;-) > >Thank you very much in advance for your help! > >Charles >
