[elvin-discuss] Re: Elvin spec

David Arnold davida at pobox.com
Wed Jan 10 22:09:12 CST 2007


-->"Ian" == Ian Lister <ilister at mantara.com> writes:

  >> neither of those error codes are _protocol_ errors.  they're
  >> Mantara-specific libelvin error codes.

  Ian> Right, because this is in reply to:

  Ian> On Wed, 3 Jan 2007, David Arnold wrote:
  >> most important is the NACK code, i think.  there's not much
  >> alternative for a client library than passing back a NOT_SUPPORTED
  >> to the application, but given it's allowable to have routers
  >> without quench, etc, it's gotta be reported somehow.

  Ian> What the client library passes back to the application is the
  Ian> API, not the protocol, and NOT_SUPPORTED is a Mantara libelvin
  Ian> error code.

ok.

what is required, i think, is a way for the router to inform the client
library that a requested feature is not supported.  i'm proposing that
we use Nack error code 2007 for this.

whether a client library enables an application to distinguish between
NOT_SUPPORTED and NO_ROUTER_SUPPORT, and how it choses to report those
conditions, is beyond the scope of the protocol spec, imo.




d


More information about the elvin-discuss mailing list