[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Back end functions

Christopher Ambler wrote:
> Ignoring that fact that we have yet to determine that there is even
> going to be a 'back end' at all, assuming there were, an API is about
> as far as it should go. That API, in fact, should be specified by
> CORE, or whatever takes the duties of CORE, to insure that all
> registrars go into this knowing what API they will be coding for.

  May I quibble, please?
  API is a popular term, but it's really insufficient: a protocol
is probably waht we're talking about (ie, an api with an encoding
and a specific order of operations).
  Mind you, I'd also tend to say a ``lightweight protocol'', because
people often think of rocket science when I say protocol (:-))


--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | astonish the rest.        -- Mark Twain
Willowdale, Ontario   | davecb@hobbes.ss.org, canada.sun.com
N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb