Migrate SSL version from 4.0 to 4.5
Hi,
I am going to migrate application from SSL Developer Kit 4.0 to 4.5. Please let me 2 questions.
1. What property name is SSL_OPT_DISTRIBUTOR with SSL Developer Kit 4.0 in version 4.5?
2. What function name is sslDismount with SSL Developer Kit 4.0 in version 4.5?
Kind Regards,
Best Answer
-
For the first question, in SSL API 4.5, it could be SSL_OPT_IPC_HOST_NAME. This option is for retrieving the host name of the SSL IPC peer to which the channel is connected.
For the second question, there is no sslDismount method in SSL API 4.5. In SSL API 4.5, you can post the SSL_ET_SESSION_DISMOUNT event instead. This event is used by an application to notify its peer that the specified channel previously established via sslMsgMount(), sslSnkMount(), sslSrcMount(), or an SSL_ET_SESSION_REQ event is terminated.
0
Answers
-
Hello @yk0603.korea,
I would not recommend migrating to SSL 4.5, as it is End Of Life API. Please see this relevant discussion thread.
I would encourage you to consider migrating to the new, efficient and supported Elektron C/C++ APIs. Refer to the following relevant learning materials for more info:
0 -
Hello @""zoya.farberov,
Thanks for your reply.
I know SSL 4.5 is not recommended from you.
But I have no time until launching our new application. So once, I want to implement application using SSL 4.5 as simple updating. Then I will migrate to Elektron C++ API as other projects.
Therefore, if you are possible, could you please answer to my 2 questions?
Kind Regards,
0 -
Hello @yk0603.korea,
Unfortunately, we can not help with this, however:
- We expect that you will find it faster to code and much easier to use supported API. It is well-documented on this portal, you will not need to do research and will be able to re-use much of the example code available for download.
- There is a risk of taking longer to code, and incurring more cost, by using unsupported API.
- Our clients find this forum to be an excellent resource for day-to-day work with Elektron APIs.
- Out of the two, EMA = ease of use and ETA = low-level, I would target EMA, to save you the implementation time.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛