> My organization has encountered a number of pitfalls along the
> way, and I'd
> be glad to impart some of my wisdom on to you, answer your questions, or
> help you out however I can. Be forewarned though, we don't use a lot of
> OpenSRS's commands, just the ones we need. Makes sense, huh?
Makes total sense! And not only do some people only use some commands, but
everyone has their own way of storing data locally in their development
platform
of choice. :)
So, perhaps what we should do is focus on creating "base" classes
or functions for the client in whatever languages.
I use PHP, so what I'm working on is an OpenSRS base class that
has only a few public functions:
connect()
disconnect()
is_connected()
read_plain()
write_plain()
read_encrypted()
write_encrypted()
... and some private ones:
fail()
log()
show_log()
encrypt()
decrypt()
This way, anyone who wants to use PHP can write their own class
that extends the base class. User-made extended classes would
have all the code to convert from your own data constructs to the
appropriate OpenSRS commands. Things like:
register_domain()
whois()
change_contact()
... etc.
This would be a Good Way (tm) of doing things, IMHO: create a bunch
of base classes for different languages, and let the users develop
their own extensions. Comments?
__________________________________________________________________
Colin Viebrock easyDNS Technologies
control your domain
http://www.easyDNS.com
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:22 EDT