Re: Lists and EPP

Hi all,

At the risk of opening a bad can of worms ... An alternative to
the 'long' list could be to add a reference to the 'next' object
similar to the 'DNSSEC zone walk' way. It preserves the EPP object
style and allows to generate a list on the receivers side.
On the bad side, it does not provide a unique view as things might
change while retrieving the list although I guess that as a registrar
you wouldn't care to much if you can do this on a regular base, say
once a day or so.

It might produce some heavy load on registry systems though.
(But then again, we had to think more like registrars and less
like registries ?)

Fitting a round peg in hexagonal shape hole ?

-jan-



> On 9 jun 2011, at 05.14, [email protected] wrote:
>
>> Registrars which implemented agile clients had foresight.
>
> It is not that simple...
>
> A registrar have one user interface, regardless of whether it is a web
> page or API. That exposes a certain business logic to the registrants.
>
> The registry then translates the business logic regarding registration,
> renewal, transfer etc into the specific logic that the registry in
> question require.
>
> This implies both changes in the business logic and epp requirements.
>
> And in many cases it does not matter how agile clients you have...because
> the way renewal works for example, and requirements from the registry that
> certain things must be exposed to the registrant and what not.
>
>    Patrik
>
> _______________________________________________
> provreg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/provreg
>

_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg