[Rets-dev] Re: Re: Problems with Digest....

[mhb1 at se-tel.com]

Thanks for the reply! This also explains why when I tried later, with the
default Digest Implementation that comes with the .NET framework that it
worked. So... servers that DO authenticate clients under RETS 1.5 use the
cnonce value as defined in the RETS specification. Otherwise, the default
cnonce value is used as defined in RFC2617? Servers that are RETS 1.7
compatible use the cnonce value as defined by RFC2617 and use a seperate
header altogether to do client authentication? (Just making sure I
understand this..)And so for RETS servers that DO NOT use client
authentication I should just be able to use any good default
implementation of Digest Authentication? My other question is has there
been anyone that has gotten the System.Net.WebClient class in .NET to
connect to the demo.crt.realtors.org implementation of RETS Server? I can
only get System.Net.HTTPWebRequest to work. It would be so much more
helpful to use the WebClient so I can change URIs without creating a new
instance of the HTTPWebRequest class each time (since the URI property is
read-only).

Also, I was wondering why CRT didn't just use the existing HTTP protocol
in conjunction with SOAP or WSDL, since RETS developed after SOAP and
WDSL? Portions of the standard seem just to reinvent the wheel when
something that had already been defined could have been used? I was just
curious as to the thinking behind this. I mean especially since the actual
data is transfered as XML and is done so in a way that is virtually
independent of the protocol (other than for transport of course).

Anyway, again, thanks for the reply. I think once I get this
implementation finished, and if the company I work for approves it, I will
post it on SourceForge and turn it over to the Open Source community. I
feel like there is a dire need for a *native* .NET implementation of this
protocol and it might help out the industry. Especially since .NET is so
popular now. It would be good for people to see an example of how this
might be done in a .NET language. I know this is something that I have
found very fustrating in my attempts here to put this thing together. I
know other people out there must be doing it, but noone seems to want to
share their findings.