Important Changes to the Matchcode APIs
Background
Prior to the Y11M05 release, and historically, there were two ways to integrate Matchcode into your bespoke solution. The first, recommended, way was to integrate the "Client API" which builds a Client/Server solution where client applications communicate over your local network (via TCP/IP) to one or more Matchcode server processes via the Capscan Pool Manager service running on a centralised server machine.
The second way was to integrate the "Matchcode 5 Standalone API" where your solution just linked to a self-contained Matchcode library. This legacy API used a different set of function calls and structures to the "Client API" and has been deprecated for over 4 years.
The Way Forward
From the Y11M05 release onwards there will be just one unified API. Existing customer solutions using the Client API require no changes. The Client API can now additionally be configured to run in Standalone Mode. Developers of new integrations and customers who have already integrated the Client API will be able to choose/change their method of operation without changing a line of their code. Please refer to the Matchcode Client API Guide for details.
Legacy Systems
If your solution is integrated with the old "Matchcode 5 Standalone API" and you are seeking to update your Matchcode library please contact Capscan Technical Support on 020 7428 1278 or email support@capscan.com.
|