Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Elektron /
  • EMA /
avatar image
Question by Paolo Parlapiano · Aug 30 at 05:52 AM · emapostingsfcmigration

Migrating from SFC to EMA, off-stream vs on-stream posting

Hi,

migrating from an SFC C++ based application to an EMA C++ based application, I'm re-coding a module responsible of sending contribution post requests.

I just want a confirmation of my analysis.

In SFC, I used a class implementing RTRInsertServiceClient and RTRInsertClient, and the application was designed to send contribution requests to items that were not subscribed by the application itself. Using EMA, I understand that the correct way to be aligned with the old SFC application would be using off-stream posting, which allows me to send post messages over the Login stream with the target service. Instead, on-stream posting would require to register to the item target of the post requests.

So, is actually off-stream posting the strategy that I should adopt? Or it is irrelevant?

Could you please comment \ add any details clarifying the reason why off-stream and on-stream posting exist as concepts, and what are the use cases were one is preferable to the other?

Thanks

Best Regards,

Paolo

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Umer Nalla · Aug 30 at 06:36 AM

Hi @Paolo Parlapiano

Based on your description, off-stream posting would be the appropriate technique to use.

In terms of the reason why on-stream and off-stream exist - this would be to cater for the two scenarios

  1. Like your requirement where you are only interested in contributing data to an instrument - with no interest in the instrument's current values - Off-Stream would be used.
  2. When you are interested in the current values of an instrument as well as needing to contribute values to the instrument - On-stream can be used.
Comment

People who like this

0 Show 1 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

avatar image
Paolo Parlapiano · Aug 30 at 06:42 AM 0
Share

Thank you @Umer Nalla

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
8 People are following this question.

Related Questions

OMM and Record Templates 1 Answer

Migrating from RFA to EMA - Dictionary management and access 9 Answers

How to Post with EMA C++ 2 Answers

[JAVA EMA] Alternative to Posting data to TR Contribution Channel 1 Answer

ATS_INSERT_S fails via EMA PostMsg 2 Answers

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Elektron Data Platform
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges