[
https://issues.apache.org/jira/browse/MINIFICPP-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Dyer updated MINIFICPP-893:
----------------------------------
Description:
The OPC UA architecture consists of servers and clients. The clients read the
values from the OPC UA servers. We need a processor that behaves like an OPC UA
client. An individual minifi agent needs the ability to support multiple OPC UA
clients to connect to different UA servers. The client should behave something
like "ListenTCP" where a separate thread is spun up so the client can listen to
and receive events from the server in realtime and have much more fine grained
control over its scheduling.
Actually thinking about this since the protocol is Request/Response based and
the client must initiate the request for data it might not make since to have
the processor run in a separate thread but rather behave like the other
processors so a user could setup the processor to say be scheduled every 5
seconds to read data from the server.
was:The OPC UA architecture consists of servers and clients. The clients read
the values from the OPC UA servers. We need a processor that behaves like an
OPC UA client. An individual minifi agent needs the ability to support multiple
OPC UA clients to connect to different UA servers. The client should behave
something like "ListenTCP" where a separate thread is spun up so the client can
listen to and receive events from the server in realtime and have much more
fine grained control over its scheduling.
> OPC UA Client Implementation
> ----------------------------
>
> Key: MINIFICPP-893
> URL: https://issues.apache.org/jira/browse/MINIFICPP-893
> Project: Apache NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Jeremy Dyer
> Assignee: Arpad Boda
> Priority: Major
>
> The OPC UA architecture consists of servers and clients. The clients read the
> values from the OPC UA servers. We need a processor that behaves like an OPC
> UA client. An individual minifi agent needs the ability to support multiple
> OPC UA clients to connect to different UA servers. The client should behave
> something like "ListenTCP" where a separate thread is spun up so the client
> can listen to and receive events from the server in realtime and have much
> more fine grained control over its scheduling.
> Actually thinking about this since the protocol is Request/Response based and
> the client must initiate the request for data it might not make since to have
> the processor run in a separate thread but rather behave like the other
> processors so a user could setup the processor to say be scheduled every 5
> seconds to read data from the server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
