Hi Lynn
I don't have a causal explanation for the process, but I think that I can explain the logic.
HTTP return status 202 implies that the request itself is being handled in an asynchronous fashion, i.e. (for POST) the entity is not "created" immediately.
Most of the Open APIs are (presumably) being implemented in software, and there is no apparent reason why creation should take a significant amount of time, so significant that there would be no immediate response. Of course the state of the entity can change afterwards, due to processes, e.g. validation might not happen immediately. So the consumer should be prepared to consume entity state change events (for those APIs that raise such).
Specifically for Service Activation (640) and Resource Activation (702), where the implementation is (likely) by network elements, it is plausible that there could be a significant delay in entity "creation", since the "creation" in this case is the actual activation of the service or the resource in the network equipment. These two APIs certainly should allow 202 response status.
Having said that, I can understand why it might make sense for other APIs, e.g. asynchronous submission of an order via a message bus, so perhaps it should be reconsidered. It could be for more prosaic reasons, e.g. the Open API internal tooling not supporting generation of 202 in the swagger files.
Let's see what other experts have to say, they might for example want to trash my argument :).
@Ludovic Robert,
@Vance Shipley,
@Kamal MaghsoudlouAnyway hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 05, 2021 09:46
From: Lynn Dueck
Subject: 202 Accepted
I've seen threads that mention some or maybe all of the ordering specs (622, 641, 652) used to have 202 Accepted on POST but that this has been removed in the current version of the specs.
Can someone explain the background of why 202 would no longer be supported and whether that is something there has been discussion about re-introducing it?
thanks,
Lynn
------------------------------
Lynn Dueck
Oracle Corporation
------------------------------