Skip to content

Commit d0f66a7

Browse files
authored
Fixed bullet
1 parent 5dc6c28 commit d0f66a7

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

graph/patterns/longRunningOperations.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,21 +26,23 @@ There are two flavors of this solution:
2626
- The returned resource is the targeted resource and includes the status of
2727
the operation. This pattern is often called RELO (resource-based
2828
long running operation).
29-
//image
29+
3030
<!-- markdownlint-disable MD033 -->
3131
<p align="center">
3232
<img src="RELO.gif" alt="The status monitor LRO flow"/>
3333
</p>
3434
<!-- markdownlint-enable MD033 -->
35+
3536
- The returned resource is a new API resource called 'Stepwise Operation' and
3637
is created to track the status. This LRO solution is similar to the concept
3738
of Promises or Futures in other programming languages.
38-
//image
39+
3940
<!-- markdownlint-disable MD033 -->
4041
<p align="center">
4142
<img src="LRO.gif" alt="The status monitor LRO flow"/>
4243
</p>
4344
<!-- markdownlint-enable MD033 -->
45+
4446
The RELO pattern is the preferred pattern for long running operations and should be
4547
used wherever possible. The pattern avoids complexity, and consistent resource
4648
presentation makes things simpler for our users and tooling chain.

0 commit comments

Comments
 (0)