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

Re: XMLCONF Proposal

To: phil@juniper.net
Subject: Re: XMLCONF Proposal
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Thu, 20 Feb 2003 10:08:03 +0100
Cc: david.putzolu@intel.com, xmlconf@ops.ietf.org
In-reply-to: <200302192009.h1JK9Nci049861@idle.juniper.net> (message from PhilShafer on Wed, 19 Feb 2003 15:09:23 -0500)
References: <200302192009.h1JK9Nci049861@idle.juniper.net>

>>>>> Phil Shafer writes:

Phil> The XMLCONF RPC mechanism is really a shim that can be easily
Phil> placed on any RPC technology. It should allow future protocol
Phil> mappings to any of the mentioned RPCs.

I am not sure what RPC over RPC gives me. I am not even sure that what
you call RPC in the xmlconf ID is what I would call an RPC (= Remote
Procedure Call). But I have to read the document more carefully before
I can form an opinion on such esoteric questions. ;-)

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>

References:
- Re: XMLCONF Proposal
  - From: Phil Shafer <phil@juniper.net>

Prev by Date: Re: XMLCONF Proposal
Next by Date: Re: XMLCONF Proposal
Previous by thread: Re: XMLCONF Proposal
Next by thread: egads....
Index(es):
- Date
- Thread