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
When just updating local information we don't need the value of a context attribute.
mongoUpdateContext doesn't return the value of the attributes from the incoming request, and that is OK.
However, when a forward of the Update is to be done, the value of the attribute is necessary.
Right now, the service routine (postUpdateContext) adds the attribute values from the request to the response from mongoUpdateContext, so everything works, however it is slower. mongoBackend throws away information that we later have to lookup ...
The 'fix' would be to make mongoUpdateContext return the value (and type) of all attributes that are to be forwarded.
Effort: 2 man day
The text was updated successfully, but these errors were encountered:
To have all the information in the same place, just another opinion/thought (mine :) in this comment.
I agree in that it is more efficient that way (you save the lookup step in serviceRoutine) but worse from the point of view of software layers autonomy and separation of concerns.
fisuda
pushed a commit
to fisuda/fiware-orion
that referenced
this issue
Feb 15, 2022
When just updating local information we don't need the value of a context attribute.
mongoUpdateContext doesn't return the value of the attributes from the incoming request, and that is OK.
However, when a forward of the Update is to be done, the value of the attribute is necessary.
Right now, the service routine (postUpdateContext) adds the attribute values from the request to the response from mongoUpdateContext, so everything works, however it is slower. mongoBackend throws away information that we later have to lookup ...
The 'fix' would be to make mongoUpdateContext return the value (and type) of all attributes that are to be forwarded.
Effort: 2 man day
The text was updated successfully, but these errors were encountered: