#11 Object model design
I may completely incorrect in my thinking here but I am
having trouble with the design of the request/response
objects.
Essentially I am trying to create a toolkit that works
with multiple registrars using different base toolkits as
not one tool kit seems to be able to connect to all
registries.
My structure is simple: a Session object that holds all
responses from the server. This model works fine with
the NeuLevel toolkit but not with this one.
For e.g. I would like to do
EPPResponse epp_res = ((EppObjectBase)
eppClient.processAction(blah)).getResponse();
and then leave the processing of the response to the
implementations of a RegistryObject interface.
Currently I cannot do this as there is no base class
that the objects are derived from - EPPDomainCheck,
EPPContactCheck etc are implementations from epp_Action
which has no useful functionlity in this respect.
Any thoughts? Am I full of the smelly stuff? Is my
object model structred incorrectly?
Cheers
Sumit
Logged In: YES
user_id=211976
ok, we're looking at this now... a more intelligent response
will follow in the next couple of days.
Logged In: YES
user_id=211976
this has really fallen to the side. my apoligies for that
(old company had me focusing on other business/work).
We are going to refactor the package names in the RTK to
support multiple EPP versions. Something like
"com.tucows.oxrs.epp0604....". Will this solve your problem?