Hi Jimmy,
Could you please give us more ellaborations on the "cached" and "real-time"
interface?
To my understanding, for a cached interface, the data we get could be outdated
because the data are cached and they may be inconsistent with the actual status
of the resources. For the real-time interfaces, the data returned are the most
up-to-date. Is that correct?
For Holmes, its correlation analysis is based on the topology information from
A&AI. For the accuracy purpose, we need the latest topo data to support our
business. Meanwhile, we have to take the performance of our analysis into
consideration as well. For this type of scenario, which approach do you think
is better for us?
Thanks.
Guangrong
原始邮件
发件人： <[email protected]>
收件人： <[email protected]>付光荣10144542
抄送人： <[email protected]>
日 期 ：2017年08月22日 21:29
主 题 ：RE: [onap-discuss] [aai] A Question On the X-FromAppId in Request Headers
Hi, Kanagaraj,
That’s not entirely true – while A&AI does not require pre-registration of the
X-FromAppId header or enforce the use of only pre-registered application Ids,
there are conditions where we need to take special handling of requests from
certain clients. A&AI has a cached and a real-time interface some systems need
to always access the real-time interface so we pre-register their application
Id to force the use of the real time connection to the graph db.
Thanks,
jimmy
From: Kanagaraj Manickam [mailto:[email protected]]
Sent: Tuesday, August 22, 2017 4:13 AM
To: [email protected] FORSYTH, JAMES <[email protected]>
Cc: [email protected]
Subject: RE: [onap-discuss] [aai] A Question On the X-FromAppId in Request
Headers
Hi,
While I was working on robot demo scripts, I realized that x-FromAppid is just
for an auditing purpose and there is no strict naming restriction. !
Regards
Kanagaraj M
***************************************************************************************
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**************************************************************************************
***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive
this e-mail in error, please notify the sender by phone or email immediately
and delete it!
***************************************************************************************
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: 22 August 2017 12:09
To: [email protected]
Cc: [email protected]
Subject: [onap-discuss] [aai] A Question On the X-FromAppId in Request Headers
Hi Jimmy,
I've read the API docs (v11) and in it, there's a sentence saying "The
X-FromAppId will be assigned to each application by the AAI team". Does that
mean for the components that need to access AAI are required to get this ID
allocated by the AAI team. Otherwise they will not be able to get/push data
from/to AAI? Or is it, just like what the document says, is just for logging
and diagonostic purposes?
Best Regards,
Guangrong
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
