You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
klauer
changed the title
Long-term, I wonder if we should consider moving the data source from CA to [Kafka](https://github.com/jwlodek/ADPluginKafka) or less preferably PVA? This sort of consistency issue is just non-existent there.
Long-term: support different data sources and prefer them over Channel Access
Jun 3, 2021
Good question. I'm not very knowledgeable about Kafka, but replacing PVAccess with standard protocols where we are able to is, in my opinion, probably a good path forward. I'll ask around out of curiosity.
Fair point that PVA is already deployed - I suppose we should support it regardless.
Oh I absolutely agree, standard protocols are the way to go where possible. This will make the user experience and the developer experience much better.
Consider moving the primary data source from EPICS Channel Access (CA) to Kafka or (less preferably) PVAccess.
This sort of consistency issue is just non-existent when you have a single data structure containing all the necessary information to decode an image.
Originally posted but modified by @klauer in #3 (comment)
The text was updated successfully, but these errors were encountered: