>Already handled - any of our resellers can point their
>current
>installation at an OpenHRS instance and be up and running
>on their own
>tag. A new service contract is required and the fees
>payable are
>different, but in a lot of respects, it is like getting
>your own OpenSRS
>(and all of the back-end knobs and dials to go with it).
>We first
>launched this in 2001 - since then quite a few registrars
>have bought
>into the product...
Ok, now I'm really confused. This sounds to me like you're
saying the "API" has allready been abstracted into a
different presentation which is more "registry like", but
with a different payment model.
So why is'nt this unified across all users? Tucows has
allready accepted responsibilty for producing a turn key
client (witness the PERL code) and thus "the problem" that
exists seem to be,
1) Design Limitations of that current (PERL/OpenSRS)
system
2) No cross platform ("agnostic") support
So to me this suggests you have a solution allready in
place for (1) and operational the closely mirrors raw
registry API (thus previously mentioned value adds and
adressing (2)).
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:42 EDT