Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

* a client can hold connection open no matter if we require a response or just 202 * client goes down is similar for 202 * the use case demand immediate response anyway, shouldn't have human involved * this one is a good point, server won't have a chance to validate response and notify client on any error I see your point, i'm thinking since the current case is simple enough, no need polling, not much validation, and don't expect delay response etc. thinking to just go with sync path and as situation comes up we go to async? can avoid premature optimization this way i think

LoveProgramming
– LoveProgramming

2020-08-04 18:37:23 +00:00
Commented Aug 4, 2020 at 18:37
1

Just laying out the situation, its up to you to decide what goes.

Kain0_0
– Kain0_0

2020-08-04 23:37:34 +00:00
Commented Aug 4, 2020 at 23:37

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »