Skip to Content

How "at risk" are the deprecated adapters?

Feb 13, 2017 at 08:02 PM


avatar image
Former Member

I've been battling with the problem that both the ESP Socket adapter (toolkit_socket_xmllist_input) and a third party data delivery program both operate in socket client mode. One of them has to be a server.

It turns out that there are deprecated adapters (dsv_sockin_in/out)which work perfectly for my needs. They operate in server mode, and they don't have the behavior problems I'm having with the toolkit based adapters (delayed delivery of the most recent event and occasional phantom events where all values are null).

The client is understandably concerned by the fact these adapters are deprecated and wants to know if there's a timeline for when they will be removed from a future release.

Is there any reason why they can't be retained indefinitely considering that their removal would impact existing customer solutions (e.g. made "not deprecated")?

I know this question should be submitted in an incident (and probably will), but I just wanted to see what kind of response it gets in the community forum.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Robert Waywell
Feb 14, 2017 at 01:50 PM

Deprecated features should not be used for new development. The purpose of identifying a feature - in this case an adapter - as deprecated is to give advance notice that the feature will be dropped in a future release and provide reasonable lead time for Customers to upgrade to the recommended replacement.

10 |10000 characters needed characters left characters exceeded