Hi,
I find that the Java API is lacking in the sense that it really doesn't
provide a robust way of communicating with the registry. By this I mean
recovering from errors, re-attempting executions of RRP commands which have
failed due to transient server errors, maintaining an active session with
the registry in the face of session termination from time to time. It is
clear that an additional layer of code needs to be added on top of the
existing API to achieve these goals.
After reading some of the existing Java API code I am convinced that it
could have been better engineered. For example, RRP commands should not be
mere function calls, instead they should be objects that are first created
and then processed. This would essentially serialize the function call so
that it may be reattempted if a transient server error is detected.
I am contemplating modifying/rearranging some of the Java API code so that
it may suit my goals.
Has anyone has already done this work, might this be publicly available
somewhere?
---------
See http://www.verisign-grs.net/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 13:12:02 EDT