|
From: John R. <joh...@gm...> - 2004-11-01 17:47:19
|
This change is currently proposed as a change to the library (I don't think there is a list of proposed changes out there publicly at this time). Dave Dribin - is this change something that we are going to put into the next minor version release? It was one of the patches sent by John Sirois. John On 29 Oct 2004 17:23:11 -0500, Frank Kurzawa <fku...@to...> wrote: > 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. > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Cart-users mailing list > Car...@li... > https://lists.sourceforge.net/lists/listinfo/cart-users > -- John Rayburn Manager of Technical Services Threewide Corporation w: 304.594.8081 e: jra...@th... It's all about the data! |