[Cart-users] Capitalization problems in capabilities url's

[Frank K. <fku...@to...>]

I've just started using the rets-client library in CART.

Cart is very specific about what keys it will accept for capability
URL's such as GetMetaData. In particular it only accepts those
camel-caps, not ALL CAPS such as GETMETADATA. 

I believe that's completely consistent with the RETS spec, but there are
a variety of supposedly RETS-compliant servers out there that return the
keys for capability url's in all caps. When rets-client gets such a key
during the log-in sequence it chooses to fail the log-in.

Is there a simple way to handle this in a more graceful manner with
rets-client? I understand there are provisions to in rets-client to
allow for the inevitable idiosynchrasies in different "more-or-less"
compliant RETS servers but it's not at all clear to me how to take
advantage of those capabilities in rets-client.

Thanks in advance,


-- 
Frank Kurzawa <fku...@to...>
Topaz Software, Inc.