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

Re: more on ASN.1 and SOAP

It should be possible to negotiate the use of ASN.1 using the
Accept-Encoding HTTP header.  If one party didn't support ASN.1,
both could fall back to plain text or gzip.

Ted.

On Thursday, June 19, 2003, at 11:01 AM, Margaret Wasserman wrote:


So, they'd encode SOAP in ASN.1 on the wire...  Funky.

Wouldn't that eliminate the primary benefit of SOAP, which
is interoperability with huge numbers of deployed enterprise
management systems, .NET libraries, etc.?

Margaret


At 09:49 AM 6/19/2003 -0700, Randy Presuhn wrote:

Hi -

> From: "Andy Bierman" <abierman@cisco.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "netconf" <netconf@ops.ietf.org>
> Sent: Thursday, June 19, 2003 9:40 AM
> Subject: Re: more on ASN.1 and SOAP
...
> Is this for the documentation of syntax -- a replacement for XSD?
...

No.  It's about encoding rules.

Randy



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



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


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