This is to capture an idea that Jeronimo and Italo highlighted that'd be valuable for network operators to have a way to save the request parameters to reuse these on mef_eline for instance. That way, users could interactively explore the parameters and results.
The use case and implementation need to be better refined but that's the overall idea, we probably don't want to always store search results, but potentially users couldn't have a small number of stored paths and reuse those parameters (maybe users could upfront tell if they want a request ID <x> to be upserted). The resulting paths wouldn't be pre-computed and reused, they'd be only for a informational reference and for the UI to potentially highlight/draw it.
This is to capture an idea that Jeronimo and Italo highlighted that'd be valuable for network operators to have a way to save the request parameters to reuse these on
mef_elinefor instance. That way, users could interactively explore the parameters and results.The use case and implementation need to be better refined but that's the overall idea, we probably don't want to always store search results, but potentially users couldn't have a small number of stored paths and reuse those parameters (maybe users could upfront tell if they want a request ID
<x>to be upserted). The resulting paths wouldn't be pre-computed and reused, they'd be only for a informational reference and for the UI to potentially highlight/draw it.