diff options
| author |   Jose Bollo <jose.bollo@iot.bzh> | 2019-07-10 15:18:02 +0200 |
|---|---|---|
| committer | José Bollo <jose.bollo@iot.bzh> | 2019-07-12 18:26:00 +0200 |
| commit | bc38af3e79fbd6256c209a0673601832429e7418 (patch) | |
| tree | 4d9d14c0abce569585cf71fd36b56e3f0560df53 /docs | |
| parent | c8cc0d6f3df5bb3eac75ee2665639fc0ab2c35fe (diff) | |
afb-xreq: Forbids (un)subscribes after reply
Allowing to subscribe to a request that was replied
was possible and lead to problem revealed by issues
SPEC-2542 and SPEC-2599 (these issues are more related
to processing unordered incoming messages).
The choice was
- fix the bug and authorize (un)subscribe after reply
- forbids to (un)subscribe after reply
Second solution was chosen for its simplicity and
its networking efficiency.
Bug-AGL: SPEC-2542
Bug-AGL: SPEC-2599
Change-Id: I09f48b760b1fd6f70d42b80df3c8053696c45966
Signed-off-by: Jose Bollo <jose.bollo@iot.bzh>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/reference-v3/func-req.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/reference-v3/func-req.md b/docs/reference-v3/func-req.md index a70fb750..c84077d1 100644 --- a/docs/reference-v3/func-req.md +++ b/docs/reference-v3/func-req.md @@ -531,6 +531,8 @@ int afb_req_subcall_sync( * Establishes for the client link identified by 'req' a subscription * to the 'event'. * + * Establishing subscription MUST be called BEFORE replying to the request. + * * @param req the request * @param event the event to subscribe * @@ -549,6 +551,8 @@ int afb_req_subscribe( * link identified by 'req'. * Returns 0 in case of successful subscription or -1 in case of error. * + * Revoking subscription MUST be called BEFORE replying to the request. + * * @param req the request * @param event the event to revoke * |