[arin-discuss] Bringing back IP resource Request Templates
jcurran at arin.net
Mon Apr 2 16:24:36 EDT 2012
On Apr 2, 2012, at 3:57 PM, Alec Ginsberg wrote:
> One backend system.. Pretty front end web ui. Email, jms. Any web service choice.
Actually, you are describing what we now have - One backend
system, with ARIN Online (human web), RESTful (programmatic),
and email based interfaces. We don't give any web service
choice, but then again, the discussion in this thread is
about folks aren't using any programmatic interface...
As someone noted, this is exactly why during maintenance
each interface behaved as it did: Humans get an message
at attempted login, RESTful programs get an error code,
and email is queued. It's all one system with three
distinct access methods.
The email template issue is that we did not reimplement all
of the request types in the rebuilt email templates as it
would have been significantly more development, and would
would increase the maintenance costs of the entire system.
We presently need to make sure that policy changes end up
in ARIN Online, and then (as quickly as possible) end up
in the RESTful interface. Regardless of your enterprise
integration approach, you need to arrange for validation
of input from each access method, and supporting a third
access method of template-based email will mean that any
policy changes will require template and template email
It's actually not conceptually challenging at all, but if
expanded to cover all registry request types it would result
in a permanent increase in overall maintenance costs. This
is certainly an option, but should not be taken lightly since
its funded collectively by the entire community.
President and CEO
More information about the ARIN-discuss