Hi Stuart
I think we handled this in our offline discussion, but for the benefit of the wider community I will clarify that this is a defect and we need to issue a fix for TMF640 to allow return of HTTP code 202 (Pending) for POST (and PATCH) operations.
We would be pleased to hear from community members if they think any other APIs need this asynchronous response capability.
Note that many APIs support asynchronous behavior using TASK resources, where creating (POSTing) the task creates a task resource synchronously and the task starts running. So if this fix is needed it will be only for operations on managed resources (e.g. Service in TMF640 Activation and Configuration).
------------------------------
Jonathan Goldberg
Amdocs Management Limited
------------------------------
Original Message:
Sent: May 22, 2019 02:10
From: Stuart Batten
Subject: TMF640 asynchronous requests
I notice in the latest release of the TMF640 API (18.5.0) that all reference to asynchronous requests has been removed. Does this mean there is no support for asynchronous activation requests, an alternative to 640 for asynch is available or this is just an oversight in the latest 640 version? Why does the document still reference Monitors?
------------------------------
Stuart Batten
Telstra Corporation
------------------------------