[
https://issues.apache.org/jira/browse/NIFI-8290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319982#comment-17319982
]
Andrea Castello commented on NIFI-8290:
---------------------------------------
Hi, [~exceptionfactory] thanks for reviewing my contribution. As you have
guessed, the WURFL Microservice client doesn't just provide a plain and simple
HTTP client access to the service, but it also has a layer of logic that is
used to better aggregate and organize device data. It also provides different
caching layers that are important to keep performance at a good level. These
are the main reasons why I'm creating a dedicated processor.
> Create an enrich processor that adds device detection data from WURFL
> ---------------------------------------------------------------------
>
> Key: NIFI-8290
> URL: https://issues.apache.org/jira/browse/NIFI-8290
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Andrea Castello
> Assignee: Andrea Castello
> Priority: Major
> Attachments: wurfl_processor.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Create a new processor that extracts device detection data from a WURFL
> service from a user-agent or a HTTP request.
> The mechanism and goal are similar to the ones of GeoIP enrich processor:
> enriching the data flow with new data.
>
> This processor will receive a User-Agent string or a set of HTTP request
> headers as FlowFile attributes and use them to get device detection data from
> a WURFL Microservice. These device detection data - AKA device capabilities -
> will be stored in the FlowFile as attributes with the name pattern
> "wurfl.<capability_name>"
>
> Attached image is a configuration example for the WURFL device detection
> processor
>
> Note:
> * WURFL Microservice Java client is released under Apache License 2.0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
