-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathAltair
50 lines (41 loc) · 877 Bytes
/
Altair
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
http://localhost:8088/api/graphql
mutation{
modifyTable(action: Create){
result
}
}
query{
listCases(status: Pending){
id
name
status
}
}
mutation{
createCase(name: "Special Relativity", dateOfBirth: "1905-01-01"){
result
}
}
mutation{
updateCase(id: "INSERT_UUID", status: Submitted){
result
caseId
}
}
mutation{
deleteCase(id: "INSERT_UUID"){
result
caseId
}
}
ws://localhost:8088/ws/graphql
subscription {
caseStatusChanged {
id,
status
}
}
If the GraphQL [publisher] web service goes down or becomes unavailable,
the GraphQL [subscriber] client simply stops receiving events.
Interestingly, an active subscription by an external client is necessary to see the tap effects.
If any events are published during a time without an active client subscription, the events get dropped (no buffering).