[
https://issues.apache.org/jira/browse/MINIFI-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990907#comment-15990907
]
Jeremy Dyer commented on MINIFI-219:
------------------------------------
[~achristianson] Yes it will depend heavily and that has been tripping me up a
little bit hence the delay. I think even if we came up with a fantastically
engineered approach we still will never be able to support 100% of all USB
devices because to your point their are just too many possibilities. I have
toyed with the idea of using Avro since it would provide a reasonable mechanism
to encapsulate messages and NiFi already utilizes it heavily. I just balked at
added that dependency so honestly I'm back at the drawing board again. Would
love to hear any ideas if you have them!
> Create GetUSB processor for reading payloads from connected USB devices
> -----------------------------------------------------------------------
>
> Key: MINIFI-219
> URL: https://issues.apache.org/jira/browse/MINIFI-219
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: C++
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
>
> LibUSB is a popular framework for interacting with USB devices on host
> machines. The spirit of this processor will be the periodically pull data
> from USB devices connected to the host running the minifi c++ instance. This
> processor is not intended to interact with filesystem connected devices but
> rather more sensor focused devices like, scales, temperature, etc where those
> values change periodically and have context around the time the values were
> acquired. The processor will expose a general mechanism to format the
> messages received from the USB device and introduce those messages to the
> nifi flowfile
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
