Source

amqpev / amqpev / spec / amqp_0-8.xml

Full commit
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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
<?xml version="1.0"?>

<!--
Copyright Notice
================
© Copyright JPMorgan Chase Bank, Cisco Systems, Inc., Envoy Technologies Inc.,
iMatix Corporation, IONA� Technologies, Red Hat, Inc., TWIST Process
Innovations, and 29West Inc. 2006. All rights reserved.

License
=======
JPMorgan Chase Bank, Cisco Systems, Inc., Envoy Technologies Inc., iMatix
Corporation, IONA� Technologies, Red Hat, Inc., TWIST Process Innovations, and
29West Inc. (collectively, the "Authors") each hereby grants to you a
worldwide, perpetual, royalty-free, nontransferable, nonexclusive license to
(i) copy, display, and implement the Advanced Messaging Queue Protocol ("AMQP")
Specification and (ii) the Licensed Claims that are held by the Authors, all
for the purpose of implementing the Advanced Messaging Queue Protocol
Specification. Your license and any rights under this Agreement will terminate
immediately without notice from any Author if you bring any claim, suit,
demand, or action related to the Advanced Messaging Queue Protocol
Specification against any Author.  Upon termination, you shall destroy all
copies of the Advanced Messaging Queue Protocol Specification in your
possession or control.

As used hereunder, "Licensed Claims" means those claims of a patent or patent
application, throughout the world, excluding design patents and design
registrations, owned or controlled, or that can be sublicensed without fee and
in compliance with the requirements of this Agreement, by an Author or its
affiliates now or at any future time and which would necessarily be infringed
by implementation of the Advanced Messaging Queue Protocol Specification. A
claim is necessarily infringed hereunder only when it is not possible to avoid
infringing it because there is no plausible non-infringing alternative for
implementing the required portions of the Advanced Messaging Queue Protocol
Specification. Notwithstanding the foregoing, Licensed Claims shall not include
any claims other than as set forth above even if contained in the same patent
as Licensed Claims; or that read solely on any implementations of any portion
of the Advanced Messaging Queue Protocol Specification that are not required by
the Advanced Messaging Queue Protocol Specification, or that, if licensed,
would require a payment of royalties by the licensor to unaffiliated third
parties.  Moreover, Licensed Claims shall not include (i) any enabling
technologies that may be necessary to make or use any Licensed Product but are
not themselves expressly set forth in the Advanced Messaging Queue Protocol
Specification (e.g., semiconductor manufacturing technology, compiler
technology, object oriented technology, networking technology, operating system
technology, and the like); or (ii) the implementation of other published
standards developed elsewhere and merely referred to in the body of the
Advanced Messaging Queue Protocol Specification, or (iii) any Licensed Product
and any combinations thereof the purpose or function of which is not required
for compliance with the Advanced Messaging Queue Protocol Specification. For
purposes of this definition, the Advanced Messaging Queue Protocol
Specification shall be deemed to include both architectural and interconnection
requirements essential for interoperability and may also include supporting
source code artifacts where such architectural, interconnection requirements
and source code artifacts are expressly identified as being required or
documentation to achieve compliance with the Advanced Messaging Queue Protocol
Specification.

As used hereunder, "Licensed Products" means only those specific portions of
products (hardware, software or combinations thereof) that implement and are
compliant with all relevant portions of the Advanced Messaging Queue Protocol
Specification.

The following disclaimers, which you hereby also acknowledge as to any use you
may make of the Advanced Messaging Queue Protocol Specification:

THE ADVANCED MESSAGING QUEUE PROTOCOL SPECIFICATION IS PROVIDED "AS IS," AND
THE AUTHORS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE
ADVANCED MESSAGING QUEUE PROTOCOL SPECIFICATION ARE SUITABLE FOR ANY PURPOSE;
NOR THAT THE IMPLEMENTATION OF THE ADVANCED MESSAGING QUEUE PROTOCOL
SPECIFICATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS
OR OTHER RIGHTS.

THE AUTHORS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF OR RELATING TO ANY USE, IMPLEMENTATION OR
DISTRIBUTION OF THE ADVANCED MESSAGING QUEUE PROTOCOL SPECIFICATION.

The name and trademarks of the Authors may NOT be used in any manner, including
advertising or publicity pertaining to the Advanced Messaging Queue Protocol
Specification or its contents without specific, written prior permission. Title
to copyright in the Advanced Messaging Queue Protocol Specification will at all
times remain with the Authors.

No other rights are granted by implication, estoppel or otherwise.

Upon termination of your license or rights under this Agreement, you shall
destroy all copies of the Advanced Messaging Queue Protocol Specification in
your possession or control.

Trademarks
==========
"JPMorgan", "JPMorgan Chase", "Chase", the JPMorgan Chase logo and the Octagon
Symbol are trademarks of JPMorgan Chase & Co.

IMATIX and the iMatix logo are trademarks of iMatix Corporation sprl.

IONA, IONA Technologies, and the IONA logos are trademarks of IONA Technologies
PLC and/or its subsidiaries.

LINUX is a trademark of Linus Torvalds. RED HAT and JBOSS are registered
trademarks of Red Hat, Inc. in the US and other countries.

Java, all Java-based trademarks and OpenOffice.org are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of
others.

Links to full AMQP specification:
=================================
http://www.envoytech.org/spec/amq/
http://www.iona.com/opensource/amqp/
http://www.redhat.com/solutions/specifications/amqp/
http://www.twiststandards.org/tiki-index.php?page=AMQ
http://www.imatix.com/amqp

-->

<amqp major="8" minor="0" port="5672" comment="AMQ protocol 0.80">
  AMQ Protocol 0.80
  <!--
  ======================================================
  ==       CONSTANTS
  ======================================================
  -->
  <constant name="frame method" value="1"/>
  <constant name="frame header" value="2"/>
  <constant name="frame body" value="3"/>
  <constant name="frame oob method" value="4"/>
  <constant name="frame oob header" value="5"/>
  <constant name="frame oob body" value="6"/>
  <constant name="frame trace" value="7"/>
  <constant name="frame heartbeat" value="8"/>
  <constant name="frame min size" value="4096"/>
  <constant name="frame end" value="206"/>
  <constant name="reply success" value="200">
    Indicates that the method completed successfully. This reply code is
    reserved for future use - the current protocol design does not use positive
    confirmation and reply codes are sent only in case of an error.
  </constant>
  <constant name="not delivered" value="310" class="soft error">
    The client asked for a specific message that is no longer available.  The
    message was delivered to another client, or was purged from the queue for
    some other reason.
  </constant>
  <constant name="content too large" value="311" class="soft error">
    The client attempted to transfer content larger than the server could
    accept at the present time.  The client may retry at a later time.
  </constant>
  <constant name="connection forced" value="320" class="hard error">
    An operator intervened to close the connection for some reason.  The client
    may retry at some later date.
  </constant>
  <constant name="invalid path" value="402" class="hard error">
    The client tried to work with an unknown virtual host or cluster.
  </constant>
  <constant name="access refused" value="403" class="soft error">
    The client attempted to work with a server entity to which it has no  due
    to security settings.
  </constant>
  <constant name="not found" value="404" class="soft error">
    The client attempted to work with a server entity that does not exist.
  </constant>
  <constant name="resource locked" value="405" class="soft error">
    The client attempted to work with a server entity to which it has no access
    because another client is working with it.
  </constant>
  <constant name="frame error" value="501" class="hard error">
    The client sent a malformed frame that the server could not decode.  This
    strongly implies a programming error in the client.
  </constant>
  <constant name="syntax error" value="502" class="hard error">
    The client sent a frame that contained illegal values for one or more
    fields.  This strongly implies a programming error in the client.
  </constant>
  <constant name="command invalid" value="503" class="hard error">
    The client sent an invalid sequence of frames, attempting to perform an
    operation that was considered invalid by the server. This usually implies a
    programming error in the client.
  </constant>
  <constant name="channel error" value="504" class="hard error">
    The client attempted to work with a channel that had not been correctly
    opened.  This most likely indicates a fault in the client layer.
  </constant>
  <constant name="resource error" value="506" class="hard error">
    The server could not complete the method because it lacked sufficient
    resources. This may be due to the client creating too many of some type of
    entity.
  </constant>
  <constant name="not allowed" value="530" class="hard error">
    The client tried to work with some entity in a manner that is prohibited by
    the server, due to security settings or by some other criteria.
  </constant>
  <constant name="not implemented" value="540" class="hard error">
    The client tried to use functionality that is not implemented in the
    server.
  </constant>
  <constant name="internal error" value="541" class="hard error">
    The server could not complete the method because of an internal error.  The
    server may require intervention by an operator in order to resume normal
    operations.
  </constant>
  <!--
  ======================================================
  ==       DOMAIN TYPES
  ======================================================
  -->
  <domain name="access ticket" type="short">
    access ticket granted by server
    <doc>
      An access ticket granted by the server for a certain set of access rights
      within a specific realm. Access tickets are valid within the channel
      where they were created, and expire when the channel closes.
    </doc>
    <assert check="ne" value="0"/>
  </domain>
  <domain name="class id" type="short"/>
  <domain name="consumer tag" type="shortstr">
    consumer tag
    <doc>
      Identifier for the consumer, valid within the current connection.
    </doc>
    <rule implement="MUST">
      The consumer tag is valid only within the channel from which the consumer
      was created. I.e. a client MUST NOT create a consumer in one channel and
      then use it in another.
    </rule>
  </domain>
  <domain name="delivery tag" type="longlong">
    server-assigned delivery tag
    <doc>
      The server-assigned and channel-specific delivery tag
    </doc>
    <rule implement="MUST">
      The delivery tag is valid only within the channel from which the message
      was received.  I.e. a client MUST NOT receive a message on one channel
      and then acknowledge it on another.
    </rule>
    <rule implement="MUST">
      The server MUST NOT use a zero value for delivery tags.  Zero is reserved
      for client use, meaning "all messages so far received".
    </rule>
  </domain>
  <domain name="exchange name" type="shortstr">
    exchange name
    <doc>
      The exchange name is a client-selected string that identifies the
      exchange for publish methods.  Exchange names may consist of any mixture
      of digits, letters, and underscores.  Exchange names are scoped by the
      virtual host.
    </doc>
    <assert check="length" value="127"/>
  </domain>
  <domain name="known hosts" type="shortstr">
    list of known hosts
    <doc>
      Specifies the list of equivalent or alternative hosts that the server
      knows about, which will normally include the current server itself.
      Clients can cache this information and use it when reconnecting to a
      server after a failure.
    </doc>
    <rule implement="MAY">
      The server MAY leave this field empty if it knows of no other hosts than
      itself.
    </rule>
  </domain>
  <domain name="method id" type="short"/>
  <domain name="no ack" type="bit">
    no acknowledgement needed
    <doc>
      If this field is set the server does not expect acknowledgments for
      messages.  That is, when a message is delivered to the client the server
      automatically and silently acknowledges it on behalf of the client.  This
      functionality increases performance but at the cost of reliability.
      Messages can get lost if a client dies before it can deliver them to the
      application.
    </doc>
  </domain>
  <domain name="no local" type="bit">
    do not deliver own messages
    <doc>
      If the no-local field is set the server will not send messages to the
      client that published them.
    </doc>
  </domain>
  <domain name="path" type="shortstr">
    <doc>
      Must start with a slash "/" and continue with path names separated by
      slashes. A path name consists of any combination of at least one of
      [A-Za-z0-9] plus zero or more of [.-_+!=:].
    </doc>
    <assert check="notnull"/>
    <assert check="syntax" rule="path"/>
    <assert check="length" value="127"/>
  </domain>
  <domain name="peer properties" type="table">
    <doc>
      This string provides a set of peer properties, used for identification,
      debugging, and general information.
    </doc>
    <rule implement="SHOULD">
      The properties SHOULD contain these fields: "product", giving the name of
      the peer product, "version", giving the name of the peer version,
      "platform", giving the name of the operating system, "copyright", if
      appropriate, and "information", giving other general information.
    </rule>
  </domain>
  <domain name="queue name" type="shortstr">
    queue name
    <doc>
      The queue name identifies the queue within the vhost.  Queue names may
      consist of any mixture of digits, letters, and underscores.
    </doc>
    <assert check="length" value="127"/>
  </domain>
  <domain name="redelivered" type="bit">
    message is being redelivered
    <doc>
      This indicates that the message has been previously delivered to this or
      another client.
    </doc>
    <rule implement="SHOULD">
      The server SHOULD try to signal redelivered messages when it can.  When
      redelivering a message that was not successfully acknowledged, the server
      SHOULD deliver it to the original client if possible.
    </rule>
    <rule implement="MUST">
      The client MUST NOT rely on the redelivered field but MUST take it as a
      hint that the message may already have been processed.  A fully robust
      client must be able to track duplicate received messages on
      non-transacted, and locally-transacted channels.
    </rule>
  </domain>
  <domain name="reply code" type="short">
    reply code from server
    <doc>
      The reply code. The AMQ reply codes are defined in AMQ RFC 011.
    </doc>
    <assert check="notnull"/>
  </domain>
  <domain name="reply text" type="shortstr">
    localised reply text
    <doc>
      The localised reply text.  This text can be logged as an aid to resolving
      issues.
    </doc>
    <assert check="notnull"/>
  </domain>
  <class name="connection" handler="connection" index="10">
    <!--
    ======================================================
    ==       CONNECTION
    ======================================================
    -->
    work with socket connections
    <doc>
      The connection class provides methods for a client to establish a network
      connection to a server, and for both peers to operate the connection
      thereafter.
    </doc>
    <doc name="grammar">
      connection          = open-connection *use-connection close-connection
      open-connection     = C:protocol-header
                            S:START C:START-OK
                            *challenge
                            S:TUNE C:TUNE-OK
                            C:OPEN S:OPEN-OK | S:REDIRECT
      challenge           = S:SECURE C:SECURE-OK
      use-connection      = *channel
      close-connection    = C:CLOSE S:CLOSE-OK
      / S:CLOSE C:CLOSE-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="MUST"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="start" synchronous="1" index="10">
      start connection negotiation
      <doc>
        This method starts the connection negotiation process by telling the
        client the protocol version that the server proposes, along with a list
        of security mechanisms which the client can use for authentication.
      </doc>
      <rule implement="MUST">
        If the client cannot handle the protocol version suggested by the
        server it MUST close the socket connection.
      </rule>
      <rule implement="MUST">
        The server MUST provide a protocol version that is lower than or equal
        to that requested by the client in the protocol header. If the server
        cannot support the specified protocol it MUST NOT send this method, but
        MUST close the socket connection.
      </rule>
      <chassis name="client" implement="MUST"/>
      <response name="start-ok"/>
      <field name="version major" type="octet">
        protocol major version
        <doc>
          The protocol major version that the server agrees to use, which
          cannot be higher than the client's major version.
        </doc>
      </field>
      <field name="version minor" type="octet">
        protocol major version
        <doc>
          The protocol minor version that the server agrees to use, which
          cannot be higher than the client's minor version.
        </doc>
      </field>
      <field name="server properties" domain="peer properties">
        server properties
      </field>
      <field name="mechanisms" type="longstr">
        available security mechanisms
        <doc>
          A list of the security mechanisms that the server supports, delimited
          by spaces.  Currently ASL supports these mechanisms: PLAIN.
        </doc>
        <see name="security mechanisms"/>
        <assert check="notnull"/>
      </field>
      <field name="locales" type="longstr">
        available message locales
        <doc>
          A list of the message locales that the server supports, delimited by
          spaces.  The locale defines the language in which the server will
          send reply texts.
        </doc>
        <rule implement="MUST">
          All servers MUST support at least the en_US locale.
        </rule>
        <assert check="notnull"/>
      </field>
    </method>
    <method name="start-ok" synchronous="1" index="11">
      select security mechanism and locale
      <doc>
        This method selects a SASL security mechanism. ASL uses SASL (RFC2222)
        to negotiate authentication and encryption.
      </doc>
      <chassis name="server" implement="MUST"/>
      <field name="client properties" domain="peer properties">
        client properties
      </field>
      <field name="mechanism" type="shortstr">
        selected security mechanism
        <doc>
          A single security mechanisms selected by the client, which must be
          one of those specified by the server.
        </doc>
        <rule implement="SHOULD">
          The client SHOULD authenticate using the highest-level security
          profile it can handle from the list provided by the server.
        </rule>
        <rule implement="MUST">
          The mechanism field MUST contain one of the security mechanisms
          proposed by the server in the Start method. If it doesn't, the server
          MUST close the socket.
        </rule>
        <assert check="notnull"/>
      </field>
      <field name="response" type="longstr">
        security response data
        <doc>
          A block of opaque data passed to the security mechanism. The contents
          of this data are defined by the SASL security mechanism.  For the
          PLAIN security mechanism this is defined as a field table holding two
          fields, LOGIN and PASSWORD.
        </doc>
        <assert check="notnull"/>
      </field>
      <field name="locale" type="shortstr">
        selected message locale
        <doc>
          A single message local selected by the client, which must be one of
          those specified by the server.
        </doc>
        <assert check="notnull"/>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="secure" synchronous="1" index="20">
      security mechanism challenge
      <doc>
        The SASL protocol works by exchanging challenges and responses until
        both peers have received sufficient information to authenticate each
        other.  This method challenges the client to provide more information.
      </doc>
      <chassis name="client" implement="MUST"/>
      <response name="secure-ok"/>
      <field name="challenge" type="longstr">
        security challenge data
        <doc>
          Challenge information, a block of opaque binary data passed to the
          security mechanism.
        </doc>
        <see name="security mechanisms"/>
      </field>
    </method>
    <method name="secure-ok" synchronous="1" index="21">
      security mechanism response
      <doc>
        This method attempts to authenticate, passing a block of SASL data for
        the security mechanism at the server side.
      </doc>
      <chassis name="server" implement="MUST"/>
      <field name="response" type="longstr">
        security response data
        <doc>
          A block of opaque data passed to the security mechanism.  The
          contents of this data are defined by the SASL security mechanism.
        </doc>
        <assert check="notnull"/>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="tune" synchronous="1" index="30">
      propose connection tuning parameters
      <doc>
        This method proposes a set of connection configuration values to the
        client.  The client can accept and/or adjust these.
      </doc>
      <chassis name="client" implement="MUST"/>
      <response name="tune-ok"/>
      <field name="channel max" type="short">
        proposed maximum channels
        <doc>
          The maximum total number of channels that the server allows per
          connection. Zero means that the server does not impose a fixed limit,
          but the number of allowed channels may be limited by available server
          resources.
        </doc>
      </field>
      <field name="frame max" type="long">
        proposed maximum frame size
        <doc>
          The largest frame size that the server proposes for the connection.
          The client can negotiate a lower value.  Zero means that the server
          does not impose any specific limit but may reject very large frames
          if it cannot allocate resources for them.
        </doc>
        <rule implement="MUST">
          Until the frame-max has been negotiated, both peers MUST accept
          frames of up to 4096 octets large. The minimum non-zero value for the
          frame-max field is 4096.
        </rule>
      </field>
      <field name="heartbeat" type="short">
        desired heartbeat delay
        <doc>
          The delay, in seconds, of the connection heartbeat that the server
          wants.  Zero means the server does not want a heartbeat.
        </doc>
      </field>
    </method>
    <method name="tune-ok" synchronous="1" index="31">
      negotiate connection tuning parameters
      <doc>
        This method sends the client's connection tuning parameters to the
        server. Certain fields are negotiated, others provide capability
        information.
      </doc>
      <chassis name="server" implement="MUST"/>
      <field name="channel max" type="short">
        negotiated maximum channels
        <doc>
          The maximum total number of channels that the client will use per
          connection.  May not be higher than the value specified by the
          server.
        </doc>
        <rule implement="MAY">
          The server MAY ignore the channel-max value or MAY use it for tuning
          its resource allocation.
        </rule>
        <assert check="notnull"/>
        <assert check="le" method="tune" field="channel max"/>
      </field>
      <field name="frame max" type="long">
        negotiated maximum frame size
        <doc>
          The largest frame size that the client and server will use for the
          connection.  Zero means that the client does not impose any specific
          limit but may reject very large frames if it cannot allocate
          resources for them.  Note that the frame-max limit applies
          principally to content frames, where large contents can be broken
          into frames of arbitrary size.
        </doc>
        <rule implement="MUST">
          Until the frame-max has been negotiated, both peers must accept
          frames of up to 4096 octets large. The minimum non-zero value for the
          frame-max field is 4096.
        </rule>
      </field>
      <field name="heartbeat" type="short">
        desired heartbeat delay
        <doc>
          The delay, in seconds, of the connection heartbeat that the client
          wants. Zero means the client does not want a heartbeat.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="open" synchronous="1" index="40">
      open connection to virtual host
      <doc>
        This method opens a connection to a virtual host, which is a collection
        of resources, and acts to separate multiple application domains within
        a server.
      </doc>
      <rule implement="MUST">
        The client MUST open the context before doing any work on the
        connection.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="open-ok"/>
      <response name="redirect"/>
      <field name="virtual host" domain="path">
        virtual host name
        <assert check="regexp" value="^[a-zA-Z0-9/-_]+$"/>
        <doc>
          The name of the virtual host to work with.
        </doc>
        <rule implement="MUST">
          If the server supports multiple virtual hosts, it MUST enforce a full
          separation of exchanges, queues, and all associated entities per
          virtual host. An application, connected to a specific virtual host,
          MUST NOT be able to access resources of another virtual host.
        </rule>
        <rule implement="SHOULD">
          The server SHOULD verify that the client has permission to access the
          specified virtual host.
        </rule>
        <rule implement="MAY">
          The server MAY configure arbitrary limits per virtual host, such as
          the number of each type of entity that may be used, per connection
          and/or in total.
        </rule>
      </field>
      <field name="capabilities" type="shortstr">
        required capabilities
        <doc>
          The client may specify a number of capability names, delimited by
          spaces.  The server can use this string to how to process the
          client's connection request.
        </doc>
      </field>
      <field name="insist" type="bit">
        insist on connecting to server
        <doc>
          In a configuration with multiple load-sharing servers, the server may
          respond to a Connection.Open method with a Connection.Redirect.  The
          insist option tells the server that the client is insisting on a
          connection to the specified server.
        </doc>
        <rule implement="SHOULD">
          When the client uses the insist option, the server SHOULD accept the
          client connection unless it is technically unable to do so.
        </rule>
      </field>
    </method>
    <method name="open-ok" synchronous="1" index="41">
      signal that the connection is ready
      <doc>
        This method signals to the client that the connection is ready for use.
      </doc>
      <chassis name="client" implement="MUST"/>
      <field name="known hosts" domain="known hosts"/>
    </method>
    <method name="redirect" synchronous="1" index="50">
      asks the client to use a different server
      <doc>
        This method redirects the client to another server, based on the
        requested virtual host and/or capabilities.
      </doc>
      <rule implement="SHOULD">
        When getting the Connection.Redirect method, the client SHOULD
        reconnect to the host specified, and if that host is not present, to
        any of the hosts specified in the known-hosts list.
      </rule>
      <chassis name="client" implement="MAY"/>
      <field name="host" type="shortstr">
        server to connect to
        <doc>
          Specifies the server to connect to.  This is an IP address or a DNS
          name, optionally followed by a colon and a port number. If no port
          number is specified, the client should use the default port number
          for the protocol.
        </doc>
        <assert check="notnull"/>
      </field>
      <field name="known hosts" domain="known hosts"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="close" synchronous="1" index="60">
      request a connection close
      <doc>
        This method indicates that the sender wants to close the connection.
        This may be due to internal conditions (e.g. a forced shut-down) or due
        to an error handling a specific method, i.e. an exception.  When a
        close is due to an exception, the sender provides the class and method
        id of the method which caused the exception.
      </doc>
      <rule implement="MUST">
        After sending this method any received method except the Close-OK
        method MUST be discarded.
      </rule>
      <rule implement="MAY">
        The peer sending this method MAY use a counter or timeout to detect
        failure of the other peer to respond correctly with the Close-OK
        method.
      </rule>
      <rule implement="MUST">
        When a server receives the Close method from a client it MUST delete
        all server-side resources associated with the client's context.  A
        client CANNOT reconnect to a context after sending or receiving a Close
        method.
      </rule>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="close-ok"/>
      <field name="reply code" domain="reply code"/>
      <field name="reply text" domain="reply text"/>
      <field name="class id" domain="class id">
        failing method class
        <doc>
          When the close is provoked by a method exception, this is the class
          of the method.
        </doc>
      </field>
      <field name="method id" domain="class id">
        failing method ID
        <doc>
          When the close is provoked by a method exception, this is the ID of
          the method.
        </doc>
      </field>
    </method>
    <method name="close-ok" synchronous="1" index="61">
      confirm a connection close
      <doc>
        This method confirms a Connection.Close method and tells the recipient
        that it is safe to release resources for the connection and close the
        socket.
      </doc>
      <rule implement="SHOULD">
        A peer that detects a socket closure without having received a Close-Ok
        handshake method SHOULD log the error.
      </rule>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
    </method>
  </class>
  <class name="channel" handler="channel" index="20">
    <!--
    ======================================================
    ==       CHANNEL
    ======================================================
    -->
    work with channels
    <doc>
      The channel class provides methods for a client to establish a virtual
      connection - a channel - to a server and for both peers to operate the
      virtual connection thereafter.
    </doc>
    <doc name="grammar">
      channel             = open-channel *use-channel close-channel
      open-channel        = C:OPEN S:OPEN-OK
      use-channel         = C:FLOW S:FLOW-OK
                          / S:FLOW C:FLOW-OK
                          / S:ALERT
                          / functional-class
      close-channel       = C:CLOSE S:CLOSE-OK
                          / S:CLOSE C:CLOSE-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="MUST"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="open" synchronous="1" index="10">
      open a channel for use
      <doc>
        This method opens a virtual connection (a channel).
      </doc>
      <rule implement="MUST">
        This method MUST NOT be called when the channel is already open.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="open-ok"/>
      <field name="out of band" type="shortstr">
        out-of-band settings
        <doc>
          Configures out-of-band transfers on this channel.  The syntax and
          meaning of this field will be formally defined at a later date.
        </doc>
        <assert check="null"/>
      </field>
    </method>
    <method name="open-ok" synchronous="1" index="11">
      signal that the channel is ready
      <doc>
        This method signals to the client that the channel is ready for use.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="flow" synchronous="1" index="20">
      enable/disable flow from peer
      <doc>
        This method asks the peer to pause or restart the flow of content data.
        This is a simple flow-control mechanism that a peer can use to avoid
        oveflowing its queues or otherwise finding itself receiving more
        messages than it can process.  Note that this method is not intended
        for window control.  The peer that receives a request to stop sending
        content should finish sending the current content, if any, and then
        wait until it receives a Flow restart method.
      </doc>
      <rule implement="MAY">
        When a new channel is opened, it is active.  Some applications assume
        that channels are inactive until started.  To emulate this behaviour a
        client MAY open the channel, then pause it.
      </rule>
      <rule implement="SHOULD">
        When sending content data in multiple frames, a peer SHOULD monitor the
        channel for incoming methods and respond to a Channel.Flow as rapidly
        as possible.
      </rule>
      <rule implement="MAY">
        A peer MAY use the Channel.Flow method to throttle incoming content
        data for internal reasons, for example, when exchangeing data over a
        slower connection.
      </rule>
      <rule implement="MAY">
        The peer that requests a Channel.Flow method MAY disconnect and/or ban
        a peer that does not respect the request.
      </rule>
      <chassis name="server" implement="MUST"/>
      <chassis name="client" implement="MUST"/>
      <response name="flow-ok"/>
      <field name="active" type="bit">
        start/stop content frames
        <doc>
          If 1, the peer starts sending content frames.  If 0, the peer stops
          sending content frames.
        </doc>
      </field>
    </method>
    <method name="flow-ok" index="21">
      confirm a flow method
      <doc>
        Confirms to the peer that a flow command was received and processed.
      </doc>
      <chassis name="server" implement="MUST"/>
      <chassis name="client" implement="MUST"/>
      <field name="active" type="bit">
        current flow setting
        <doc>
          Confirms the setting of the processed flow method: 1 means the peer
          will start sending or continue to send content frames; 0 means it
          will not.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="alert" index="30">
      send a non-fatal warning message
      <doc>
        This method allows the server to send a non-fatal warning to the
        client.  This is used for methods that are normally asynchronous and
        thus do not have confirmations, and for which the server may detect
        errors that need to be reported.  Fatal errors are handled as channel
        or connection exceptions; non-fatal errors are sent through this
        method.
      </doc>
      <chassis name="client" implement="MUST"/>
      <field name="reply code" domain="reply code"/>
      <field name="reply text" domain="reply text"/>
      <field name="details" type="table">
        detailed information for warning
        <doc>
          A set of fields that provide more information about the problem.  The
          meaning of these fields are defined on a per-reply-code basis (TO BE
          DEFINED).
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="close" synchronous="1" index="40">
      request a channel close
      <doc>
        This method indicates that the sender wants to close the channel.  This
        may be due to internal conditions (e.g. a forced shut-down) or due to
        an error handling a specific method, i.e. an exception.  When a close
        is due to an exception, the sender provides the class and method id of
        the method which caused the exception.
      </doc>
      <rule implement="MUST">
        After sending this method any received method except Channel.Close-OK
        MUST be discarded.
      </rule>
      <rule implement="MAY">
        The peer sending this method MAY use a counter or timeout to detect
        failure of the other peer to respond correctly with Channel.Close-OK..
      </rule>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="close-ok"/>
      <field name="reply code" domain="reply code"/>
      <field name="reply text" domain="reply text"/>
      <field name="class id" domain="class id">
        failing method class
        <doc>
          When the close is provoked by a method exception, this is the class
          of the method.
        </doc>
      </field>
      <field name="method id" domain="method id">
        failing method ID
        <doc>
          When the close is provoked by a method exception, this is the ID of
          the method.
        </doc>
      </field>
    </method>
    <method name="close-ok" synchronous="1" index="41">
      confirm a channel close
      <doc>
        This method confirms a Channel.Close method and tells the recipient
        that it is safe to release resources for the channel and close the
        socket.
      </doc>
      <rule implement="SHOULD">
        A peer that detects a socket closure without having received a
        Channel.Close-Ok handshake method SHOULD log the error.
      </rule>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
    </method>
  </class>
  <class name="access" handler="connection" index="30">
    <!--
    ======================================================
    ==      ACCESS CONTROL
    ======================================================
    -->
    work with access tickets
    <doc>
      The protocol control access to server resources using access tickets.  A
      client must explicitly request access tickets before doing work.  An
      access ticket grants a client the right to use a specific set of
      resources - called a "realm" - in specific ways.
    </doc>
    <doc name="grammar">
      access              = C:REQUEST S:REQUEST-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="MUST"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="request" synchronous="1" index="10">
      request an access ticket
      <doc>
        This method requests an access ticket for an access realm.  The server
        responds by granting the access ticket.  If the client does not have
        access rights to the requested realm this causes a connection
        exception.  Access tickets are a per-channel resource.
      </doc>
      <rule implement="MUST">
        The realm name MUST start with either "/data" (for application
        resources) or "/admin" (for server administration resources).  If the
        realm starts with any other path, the server MUST raise a connection
        exception with reply code 403 (access refused).
      </rule>
      <rule implement="MUST">
        The server MUST implement the /data realm and MAY implement the /admin
        realm.  The mapping of resources to realms is not defined in the
        protocol - this is a server-side configuration issue.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="request-ok"/>
      <field name="realm" domain="path">
        name of requested realm
        <rule implement="MUST">
          If the specified realm is not known to the server, the server must
          raise a channel exception with reply code 402 (invalid path).
        </rule>
      </field>
      <field name="exclusive" type="bit">
        request exclusive access
        <doc>
          Request exclusive access to the realm. If the server cannot grant
          this - because there are other active tickets for the realm - it
          raises a channel exception.
        </doc>
      </field>
      <field name="passive" type="bit">
        request passive access
        <doc>
          Request message passive access to the specified access realm.
          Passive access lets a client get information about resources in the
          realm but not to make any changes to them.
        </doc>
      </field>
      <field name="active" type="bit">
        request active access
        <doc>
          Request message active access to the specified access realm.  Acvtive
          access lets a client get create and delete resources in the realm.
        </doc>
      </field>
      <field name="write" type="bit">
        request write access
        <doc>
          Request write access to the specified access realm.  Write access
          lets a client publish messages to all exchanges in the realm.
        </doc>
      </field>
      <field name="read" type="bit">
        request read access
        <doc>
          Request read access to the specified access realm.  Read access lets
          a client consume messages from queues in the realm.
        </doc>
      </field>
    </method>
    <method name="request-ok" synchronous="1" index="11">
      grant access to server resources
      <doc>
        This method provides the client with an access ticket. The access
        ticket is valid within the current channel and for the lifespan of the
        channel.
      </doc>
      <rule implement="MUST">
        The client MUST NOT use access tickets except within the same channel
        as originally granted.
      </rule>
      <rule implement="MUST">
        The server MUST isolate access tickets per channel and treat an attempt
        by a client to mix these as a connection exception.
      </rule>
      <chassis name="client" implement="MUST"/>
      <field name="ticket" domain="access ticket"/>
    </method>
  </class>
  <class name="exchange" handler="channel" index="40">
    <!--
    ======================================================
    ==       EXCHANGES (or "routers", if you prefer)
    ==       (Or matchers, plugins, extensions, agents,... Routing is just one of
    ==        the many fun things an exchange can do.)
    ======================================================
    -->
    work with exchanges
    <doc>
      Exchanges match and distribute messages across queues.  Exchanges can be
      configured in the server or created at runtime.
    </doc>
    <doc name="grammar">
      exchange            = C:DECLARE  S:DECLARE-OK
                          / C:DELETE   S:DELETE-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="MUST"/>
    <rule implement="MUST">
      <test>amq_exchange_19</test>
      The server MUST implement the direct and fanout exchange types, and
      predeclare the corresponding exchanges named amq.direct and amq.fanout in
      each virtual host. The server MUST also predeclare a direct exchange to
      act as the default exchange for content Publish methods and for default
      queue bindings.
    </rule>
    <rule implement="SHOULD">
      <test>amq_exchange_20</test>
      The server SHOULD implement the topic exchange type, and predeclare the
      corresponding exchange named amq.topic in each virtual host.
    </rule>
    <rule implement="MAY">
      <test>amq_exchange_21</test>
      The server MAY implement the system exchange type, and predeclare the
      corresponding exchanges named amq.system in each virtual host. If the
      client attempts to bind a queue to the system exchange, the server MUST
      raise a connection exception with reply code 507 (not allowed).
    </rule>
    <rule implement="MUST">
      <test>amq_exchange_22</test>
      The default exchange MUST be defined as internal, and be inaccessible to
      the client except by specifying an empty exchange name in a content
      Publish method. That is, the server MUST NOT let clients make explicit
      bindings to this exchange.
    </rule>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="declare" synchronous="1" index="10">
      declare exchange, create if needed
      <doc>
        This method creates an exchange if it does not already exist, and if
        the exchange exists, verifies that it is of the correct and expected
        class.
      </doc>
      <rule implement="SHOULD">
        <test>amq_exchange_23</test>
        The server SHOULD support a minimum of 16 exchanges per virtual host
        and ideally, impose no limit except as defined by available resources.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="declare-ok"/>
      <field name="ticket" domain="access ticket">
        <doc>
          When a client defines a new exchange, this belongs to the access
          realm of the ticket used.  All further work done with that exchange
          must be done with an access ticket for the same realm.
        </doc>
        <rule implement="MUST">
          The client MUST provide a valid access ticket giving "active" access
          to the realm in which the exchange exists or will be created, or
          "passive" access if the if-exists flag is set.
        </rule>
      </field>
      <field name="exchange" domain="exchange name">
        <rule implement="MUST">
          <test>amq_exchange_15</test>
          Exchange names starting with "amq." are reserved for predeclared and
          standardised exchanges.  If the client attempts to create an exchange
          starting with "amq.", the server MUST raise a channel exception with
          reply code 403 (access refused).
        </rule>
        <assert check="regexp" value="^[a-zA-Z0-9-_.:]+$"/>
      </field>
      <field name="type" type="shortstr">
        exchange type
        <doc>
          Each exchange belongs to one of a set of exchange types implemented
          by the server.  The exchange types define the functionality of the
          exchange - i.e. how messages are routed through it.  It is not valid
          or meaningful to attempt to change the type of an existing exchange.
        </doc>
        <rule implement="MUST">
          <test>amq_exchange_16</test>
          If the exchange already exists with a different type, the server MUST
          raise a connection exception with a reply code 507 (not allowed).
        </rule>
        <rule implement="MUST">
          <test>amq_exchange_18</test>
          If the server does not support the requested exchange type it MUST
          raise a connection exception with a reply code 503 (command invalid).
        </rule>
        <assert check="regexp" value="^[a-zA-Z0-9-_.:]+$"/>
      </field>
      <field name="passive" type="bit">
        do not create exchange
        <doc>
          If set, the server will not create the exchange.  The client can use
          this to check whether an exchange exists without modifying the server
          state.
        </doc>
        <rule implement="MUST">
          <test>amq_exchange_05</test>
          If set, and the exchange does not already exist, the server MUST
          raise a channel exception with reply code 404 (not found).
        </rule>
      </field>
      <field name="durable" type="bit">
        request a durable exchange
        <doc>
          If set when creating a new exchange, the exchange will be marked as
          durable.  Durable exchanges remain active when a server restarts.
          Non-durable exchanges (transient exchanges) are purged if/when a
          server restarts.
        </doc>
        <rule implement="MUST">
          <test>amq_exchange_24</test>
          The server MUST support both durable and transient exchanges.
        </rule>
        <rule implement="MUST">
          The server MUST ignore the durable field if the exchange already
          exists.
        </rule>
      </field>
      <field name="auto delete" type="bit">
        auto-delete when unused
        <doc>
          If set, the exchange is deleted when all queues have finished using
          it.
        </doc>
        <rule implement="SHOULD">
          <test>amq_exchange_02</test>
          The server SHOULD allow for a reasonable delay between the point when
          it determines that an exchange is not being used (or no longer used),
          and the point when it deletes the exchange.  At the least it must
          allow a client to create an exchange and then bind a queue to it,
          with a small but non-zero delay between these two actions.
        </rule>
        <rule implement="MUST">
          <test>amq_exchange_25</test>
          The server MUST ignore the auto-delete field if the exchange already
          exists.
        </rule>
      </field>
      <field name="internal" type="bit">
        create internal exchange
        <doc>
          If set, the exchange may not be used directly by publishers, but only
          when bound to other exchanges. Internal exchanges are used to
          construct wiring that is not visible to applications.
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>

      <field name="arguments" type="table">
        arguments for declaration
        <doc>
          A set of arguments for the declaration. The syntax and semantics of
          these arguments depends on the server implementation.  This field is
          ignored if passive is 1.
        </doc>
      </field>
    </method>
    <method name="declare-ok" synchronous="1" index="11">
      confirms an exchange declaration
      <doc>
        This method confirms a Declare method and confirms the name of the
        exchange, essential for automatically-named exchanges.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="delete" synchronous="1" index="20">
      delete an exchange
      <doc>
        This method deletes an exchange.  When an exchange is deleted all queue
        bindings on the exchange are cancelled.
      </doc>
      <chassis name="server" implement="MUST"/>
      <response name="delete-ok"/>
      <field name="ticket" domain="access ticket">
        <rule implement="MUST">
          The client MUST provide a valid access ticket giving "active" access
          rights to the exchange's access realm.
        </rule>
      </field>
      <field name="exchange" domain="exchange name">
        <rule implement="MUST">
          <test>amq_exchange_11</test>
          The exchange MUST exist. Attempting to delete a non-existing exchange
          causes a channel exception.
        </rule>
        <assert check="notnull"/>
      </field>
      <field name="if unused" type="bit">
        delete only if unused
        <doc>
          If set, the server will only delete the exchange if it has no queue
          bindings. If the exchange has queue bindings the server does not
          delete it but raises a channel exception instead.
        </doc>
        <rule implement="SHOULD">
          <test>amq_exchange_12</test>
          If set, the server SHOULD delete the exchange but only if it has no
          queue bindings.
        </rule>
        <rule implement="SHOULD">
          <test>amq_exchange_13</test>
          If set, the server SHOULD raise a channel exception if the exchange
          is in use.
        </rule>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>

    </method>
    <method name="delete-ok" synchronous="1" index="21">
      confirm deletion of an exchange
      <doc>
        This method confirms the deletion of an exchange.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
  </class>
  <class name="queue" handler="channel" index="50">
    <!--
    ======================================================
    ==       QUEUES
    ======================================================
    -->
    work with queues

    <doc>
      Queues store and forward messages.  Queues can be configured in the
      server or created at runtime.  Queues must be attached to at least one
      exchange in order to receive messages from publishers.
    </doc>
    <doc name="grammar">
      queue               = C:DECLARE  S:DECLARE-OK
                          / C:BIND     S:BIND-OK
                          / C:PURGE    S:PURGE-OK
                          / C:DELETE   S:DELETE-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="MUST"/>
    <rule implement="MUST">
      <test>amq_queue_33</test>
      A server MUST allow any content class to be sent to any queue, in any
      mix, and queue and delivery these content classes independently. Note
      that all methods that fetch content off queues are specific to a given
      content class.
    </rule>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="declare" synchronous="1" index="10">
      declare queue, create if needed
      <doc>
        This method creates or checks a queue.  When creating a new queue the
        client can specify various properties that control the durability of
        the queue and its contents, and the level of sharing for the queue.
      </doc>
      <rule implement="MUST">
        <test>amq_queue_34</test>
        The server MUST create a default binding for a newly-created queue to
        the default exchange, which is an exchange of type 'direct'.
      </rule>
      <rule implement="SHOULD">
        <test>amq_queue_35</test>
        The server SHOULD support a minimum of 256 queues per virtual host and
        ideally, impose no limit except as defined by available resources.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="declare-ok"/>
      <field name="ticket" domain="access ticket">
        <doc>
          When a client defines a new queue, this belongs to the access realm
          of the ticket used.  All further work done with that queue must be
          done with an access ticket for the same realm.
        </doc>
        <doc>
          The client provides a valid access ticket giving "active" access to
          the realm in which the queue exists or will be created, or "passive"
          access if the if-exists flag is set.
        </doc>
      </field>
      <field name="queue" domain="queue name">
        <rule implement="MAY">
          <test>amq_queue_10</test>
          The queue name MAY be empty, in which case the server MUST create a
          new queue with a unique generated name and return this to the client
          in the Declare-Ok method.
        </rule>
        <rule implement="MUST">
          <test>amq_queue_32</test>
          Queue names starting with "amq." are reserved for predeclared and
          standardised server queues.  If the queue name starts with "amq." and
          the passive option is zero, the server MUST raise a connection
          exception with reply code 403 (access refused).
        </rule>
        <assert check="regexp" value="^[a-zA-Z0-9-_.:]*$"/>
      </field>
      <field name="passive" type="bit">
        do not create queue
        <doc>
          If set, the server will not create the queue.  The client can use
          this to check whether a queue exists without modifying the server
          state.
        </doc>
        <rule implement="MUST">
          <test>amq_queue_05</test>
          If set, and the queue does not already exist, the server MUST respond
          with a reply code 404 (not found) and raise a channel exception.
        </rule>
      </field>
      <field name="durable" type="bit">
        request a durable queue
        <doc>
          If set when creating a new queue, the queue will be marked as
          durable.  Durable queues remain active when a server restarts.
          Non-durable queues (transient queues) are purged if/when a server
          restarts.  Note that durable queues do not necessarily hold
          persistent messages, although it does not make sense to send
          persistent messages to a transient queue.
        </doc>
        <rule implement="MUST">
          <test>amq_queue_03</test>
          The server MUST recreate the durable queue after a restart.
        </rule>
        <rule implement="MUST">
          <test>amq_queue_36</test>
          The server MUST support both durable and transient queues.
        </rule>
        <rule implement="MUST">
          <test>amq_queue_37</test>
          The server MUST ignore the durable field if the queue already exists.
        </rule>
      </field>
      <field name="exclusive" type="bit">
        request an exclusive queue
        <doc>
          Exclusive queues may only be consumed from by the current connection.
          Setting the 'exclusive' flag always implies 'auto-delete'.
        </doc>
        <rule implement="MUST">
          <test>amq_queue_38</test>
          The server MUST support both exclusive (private) and non-exclusive
          (shared) queues.
        </rule>
        <rule implement="MUST">
          <test>amq_queue_04</test>
          The server MUST raise a channel exception if 'exclusive' is specified
          and the queue already exists and is owned by a different connection.
        </rule>
      </field>
      <field name="auto delete" type="bit">
        auto-delete queue when unused
        <doc>
          If set, the queue is deleted when all consumers have finished using
          it. Last consumer can be cancelled either explicitly or because its
          channel is closed. If there was no consumer ever on the queue, it
          won't be deleted.
        </doc>
        <rule implement="SHOULD">
          <test>amq_queue_02</test>
          The server SHOULD allow for a reasonable delay between the point when
          it determines that a queue is not being used (or no longer used), and
          the point when it deletes the queue.  At the least it must allow a
          client to create a queue and then create a consumer to read from it,
          with a small but non-zero delay between these two actions.  The
          server should equally allow for clients that may be disconnected
          prematurely, and wish to re-consume from the same queue without
          losing messages.  We would recommend a configurable timeout, with a
          suitable default value being one minute.
        </rule>
        <rule implement="MUST">
          <test>amq_queue_31</test>
          The server MUST ignore the auto-delete field if the queue already
          exists.
        </rule>
      </field>
      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>

      <field name="arguments" type="table">
        arguments for declaration
        <doc>
          A set of arguments for the declaration. The syntax and semantics of
          these arguments depends on the server implementation.  This field is
          ignored if passive is 1.
        </doc>
      </field>
    </method>
    <method name="declare-ok" synchronous="1" index="11">
      confirms a queue definition
      <doc>
        This method confirms a Declare method and confirms the name of the
        queue, essential for automatically-named queues.
      </doc>
      <chassis name="client" implement="MUST"/>
      <field name="queue" domain="queue name">
        <doc>
          Reports the name of the queue. If the server generated a queue name,
          this field contains that name.
        </doc>
        <assert check="notnull"/>
      </field>
      <field name="message count" type="long">
        number of messages in queue
        <doc>
          Reports the number of messages in the queue, which will be zero for
          newly-created queues.
        </doc>
      </field>
      <field name="consumer count" type="long">
        number of consumers
        <doc>
          Reports the number of active consumers for the queue. Note that
          consumers can suspend activity (Channel.Flow) in which case they do
          not appear in this count.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="bind" synchronous="1" index="20">
      bind queue to an exchange
      <doc>
        This method binds a queue to an exchange.  Until a queue is bound it
        will not receive any messages.  In a classic messaging model,
        store-and-forward queues are bound to a dest exchange and subscription
        queues are bound to a dest_wild exchange.
      </doc>
      <rule implement="MUST">
        <test>amq_queue_25</test>
        A server MUST allow ignore duplicate bindings - that is, two or more
        bind methods for a specific queue, with identical arguments - without
        treating these as an error.
      </rule>
      <rule implement="MUST">
        <test>amq_queue_39</test>
        If a bind fails, the server MUST raise a connection exception.
      </rule>
      <rule implement="MUST">
        <test>amq_queue_12</test>
        The server MUST NOT allow a durable queue to bind to a transient
        exchange. If the client attempts this the server MUST raise a channel
        exception.
      </rule>
      <rule implement="SHOULD">
        <test>amq_queue_13</test>
        Bindings for durable queues are automatically durable and the server
        SHOULD restore such bindings after a server restart.
      </rule>
      <rule implement="MUST">
        <test>amq_queue_17</test>
        If the client attempts to an exchange that was declared as internal,
        the server MUST raise a connection exception with reply code 530 (not
        allowed).
      </rule>
      <rule implement="SHOULD">
        <test>amq_queue_40</test>
        The server SHOULD support at least 4 bindings per queue, and ideally,
        impose no limit except as defined by available resources.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="bind-ok"/>
      <field name="ticket" domain="access ticket">
        <doc>
          The client provides a valid access ticket giving "active" access
          rights to the queue's access realm.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to bind.  If the queue name is empty,
          refers to the current queue for the channel, which is the last
          declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
        <doc name = "rule" test = "amq_queue_26">
          If the queue does not exist the server MUST raise a channel exception
          with reply code 404 (not found).
        </doc>
      </field>

      <field name="exchange" domain="exchange name">
        The name of the exchange to bind to.
        <rule implement="MUST">
          <test>amq_queue_14</test>
          If the exchange does not exist the server MUST raise a channel
          exception with reply code 404 (not found).
        </rule>
      </field>
      <field name="routing key" type="shortstr">
        message routing key
        <doc>
          Specifies the routing key for the binding.  The routing key is used
          for routing messages depending on the exchange configuration.  Not
          all exchanges use a routing key - refer to the specific exchange
          documentation.  If the routing key is empty and the queue name is
          empty, the routing key will be the current queue for the channel,
          which is the last declared queue.
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>

      <field name="arguments" type="table">
        arguments for binding
        <doc>
          A set of arguments for the binding.  The syntax and semantics of
          these arguments depends on the exchange class.
        </doc>
      </field>
    </method>
    <method name="bind-ok" synchronous="1" index="21">
      confirm bind successful
      <doc>
        This method confirms that the bind was successful.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="purge" synchronous="1" index="30">
      purge a queue
      <doc>
        This method removes all messages from a queue.  It does not cancel
        consumers.  Purged messages are deleted without any formal "undo"
        mechanism.
      </doc>
      <rule implement="MUST">
        <test>amq_queue_15</test>
        A call to purge MUST result in an empty queue.
      </rule>
      <rule implement="MUST">
        <test>amq_queue_41</test>
        On transacted channels the server MUST not purge messages that have
        already been sent to a client but not yet acknowledged.
      </rule>
      <rule implement="MAY">
        <test>amq_queue_42</test>
        The server MAY implement a purge queue or log that allows system
        administrators to recover accidentally-purged messages.  The server
        SHOULD NOT keep purged messages in the same storage spaces as the live
        messages since the volumes of purged messages may get very large.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="purge-ok"/>
      <field name="ticket" domain="access ticket">
        <doc>
          The access ticket must be for the access realm that holds the queue.
        </doc>
        <rule implement="MUST">
          The client MUST provide a valid access ticket giving "read" access
          rights to the queue's access realm.  Note that purging a queue is
          equivalent to reading all messages and discarding them.
        </rule>
      </field>
      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to purge.  If the queue name is
          empty, refers to the current queue for the channel, which is the last
          declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
        <doc name = "rule" test = "amq_queue_16">
          The queue must exist. Attempting to purge a non-existing queue causes
          a channel exception.
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>
    <method name="purge-ok" synchronous="1" index="31">
      confirms a queue purge
      <doc>
        This method confirms the purge of a queue.
      </doc>
      <chassis name="client" implement="MUST"/>
      <field name="message count" type="long">
        number of messages purged
        <doc>
          Reports the number of messages purged.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="delete" synchronous="1" index="40">
      delete a queue
      <doc>
        This method deletes a queue.  When a queue is deleted any pending
        messages are sent to a dead-letter queue if this is defined in the
        server configuration, and all consumers on the queue are cancelled.
      </doc>
      <rule implement="SHOULD">
        <test>amq_queue_43</test>
        The server SHOULD use a dead-letter queue to hold messages that were
        pending on a deleted queue, and MAY provide facilities for a system
        administrator to move these messages back to an active queue.
      </rule>
      <chassis name="server" implement="MUST"/>
      <response name="delete-ok"/>
      <field name="ticket" domain="access ticket">
        <doc>
          The client provides a valid access ticket giving "active" access
          rights to the queue's access realm.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to delete. If the queue name is
          empty, refers to the current queue for the channel, which is the last
          declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
        <doc name = "rule" test = "amq_queue_21">
          The queue must exist. Attempting to delete a non-existing queue
          causes a channel exception.
        </doc>
      </field>

      <field name="if unused" type="bit">
        delete only if unused
        <doc>
          If set, the server will only delete the queue if it has no consumers.
          If the queue has consumers the server does does not delete it but
          raises a channel exception instead.
        </doc>
        <rule implement="MUST">
          <test>amq_queue_29</test>
          <test>amq_queue_30</test>
          The server MUST respect the if-unused flag when deleting a queue.
        </rule>
      </field>
      <field name="if empty" type="bit">
        delete only if empty
        <test>amq_queue_27</test>
        <doc>
          If set, the server will only delete the queue if it has no messages.
          If the queue is not empty the server raises a channel exception.
        </doc>
      </field>
      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name="delete-ok" synchronous="1" index="41">
      confirm deletion of a queue
      <doc>
        This method confirms the deletion of a queue.
      </doc>
      <chassis name="client" implement="MUST"/>
      <field name="message count" type="long">
        number of messages purged
        <doc>
          Reports the number of messages purged.
        </doc>
      </field>
    </method>
  </class>
  <class name="basic" handler="channel" index="60">
    <!--
    ======================================================
    ==       BASIC MIDDLEWARE
    ======================================================
    -->
    work with basic content
    <doc>
      The Basic class provides methods that support an industry-standard
      messaging model.
    </doc>

    <doc name = "grammar">
      basic               = C:QOS S:QOS-OK
                          / C:CONSUME S:CONSUME-OK
                          / C:CANCEL S:CANCEL-OK
                          / C:PUBLISH content
                          / S:RETURN content
                          / S:DELIVER content
                          / C:GET ( S:GET-OK content / S:GET-EMPTY )
                          / C:ACK
                          / C:REJECT
    </doc>

    <chassis name = "server" implement = "MUST" />
    <chassis name = "client" implement = "MAY"  />

    <doc name = "rule" test = "amq_basic_08">
      The server SHOULD respect the persistent property of basic messages and
      SHOULD make a best-effort to hold persistent basic messages on a reliable
      storage mechanism.
    </doc>
    <doc name = "rule" test = "amq_basic_09">
      The server MUST NOT discard a persistent basic message in case of a queue
      overflow. The server MAY use the Channel.Flow method to slow or stop a
      basic message publisher when necessary.
    </doc>
    <doc name = "rule" test = "amq_basic_10">
      The server MAY overflow non-persistent basic messages to persistent
      storage and MAY discard or dead-letter non-persistent basic messages on a
      priority basis if the queue size exceeds some configured limit.
    </doc>
    <doc name = "rule" test = "amq_basic_11">
      The server MUST implement at least 2 priority levels for basic messages,
      where priorities 0-4 and 5-9 are treated as two distinct levels. The
      server MAY implement up to 10 priority levels.
    </doc>
    <doc name = "rule" test = "amq_basic_12">
      The server MUST deliver messages of the same priority in order
      irrespective of their individual persistence.
    </doc>
    <doc name = "rule" test = "amq_basic_13">
      The server MUST support both automatic and explicit acknowledgements on
      Basic content.
    </doc>

    <!--  These are the properties for a Basic content  -->

    <field name = "content type" type = "shortstr">
      MIME content type
    </field>
    <field name = "content encoding" type = "shortstr">
      MIME content encoding
    </field>
    <field name = "headers" type = "table">
      Message header field table
    </field>
    <field name = "delivery mode" type = "octet">
      Non-persistent (1) or persistent (2)
    </field>
    <field name = "priority" type = "octet">
      The message priority, 0 to 9
    </field>
    <field name = "correlation id" type = "shortstr">
      The application correlation identifier
    </field>
    <field name = "reply to" type = "shortstr">
      The destination to reply to
    </field>
    <field name = "expiration" type = "shortstr">
      Message expiration specification
    </field>
    <field name = "message id" type = "shortstr">
      The application message identifier
    </field>
    <field name = "timestamp" type = "timestamp">
      The message timestamp
    </field>
    <field name = "type" type = "shortstr">
      The message type name
    </field>
    <field name = "user id" type = "shortstr">
      The creating user id
    </field>
    <field name = "app id" type = "shortstr">
      The creating application id
    </field>
    <field name = "cluster id" type = "shortstr">
      Intra-cluster routing identifier
    </field>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "qos" synchronous = "1" index = "10">
      specify quality of service
      <doc>
        This method requests a specific quality of service.  The QoS can be
        specified for the current channel or for all channels on the
        connection.  The particular properties and semantics of a qos method
        always depend on the content class semantics.  Though the qos method
        could in principle apply to both peers, it is currently meaningful only
        for the server.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "qos-ok" />

      <field name = "prefetch size" type = "long">
        prefetch window in octets
        <doc>
          The client can request that messages be sent in advance so that when
          the client finishes processing a message, the following message is
          already held locally, rather than needing to be sent down the
          channel.  Prefetching gives a performance improvement.  This field
          specifies the prefetch window size in octets.  The server will send a
          message in advance if it is equal to or smaller in size than the
          available prefetch size (and also falls into other prefetch limits).
          May be set to zero, meaning "no specific limit", although other
          prefetch limits may still apply.  The prefetch-size is ignored if the
          no-ack option is set.
        </doc>
        <doc name = "rule" test = "amq_basic_17">
          The server MUST ignore this setting when the client is not processing
          any messages - i.e. the prefetch size does not limit the transfer of
          single messages to a client, only the sending in advance of more
          messages while the client still has one or more unacknowledged
          messages.
        </doc>
      </field>

      <field name = "prefetch count" type = "short">
        prefetch window in messages
        <doc>
          Specifies a prefetch window in terms of whole messages.  This field
          may be used in combination with the prefetch-size field; a message
          will only be sent in advance if both prefetch windows (and those at
          the channel and connection level) allow it.  The prefetch-count is
          ignored if the no-ack option is set.
        </doc>
        <doc name = "rule" test = "amq_basic_18">
          The server MAY send less data in advance than allowed by the client's
          specified prefetch windows but it MUST NOT send more.
        </doc>
      </field>

      <field name = "global" type = "bit">
        apply to entire connection
        <doc>
          By default the QoS settings apply to the current channel only.  If
          this field is set, they are applied to the entire connection.
        </doc>
      </field>
    </method>

    <method name = "qos-ok" synchronous = "1" index = "11">
      confirm the requested qos
      <doc>
        This method tells the client that the requested QoS levels could be
        handled by the server.  The requested QoS applies to all active
        consumers until a new QoS is defined.
      </doc>
      <chassis name = "client" implement = "MUST" />
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "consume" synchronous = "1" index = "20">
      start a queue consumer
      <doc>
        This method asks the server to start a "consumer", which is a transient
        request for messages from a specific queue. Consumers last as long as
        the channel they were created on, or until the client cancels them.
      </doc>
      <doc name = "rule" test = "amq_basic_01">
        The server SHOULD support at least 16 consumers per queue, unless the
        queue was declared as private, and ideally, impose no limit except as
        defined by available resources.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "consume-ok" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "read" access
          rights to the realm for the queue.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to consume from.  If the queue name
          is null, refers to the current queue for the channel, which is the
          last declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
      </field>

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Specifies the identifier for the consumer. The consumer tag is local
          to a connection, so two clients can use the same consumer tags. If
          this field is empty the server will generate a unique tag.
        </doc>
        <doc name = "rule" test = "todo">
          The tag MUST NOT refer to an existing consumer. If the client
          attempts to create two consumers with the same non-empty tag the
          server MUST raise a connection exception with reply code 530 (not
          allowed).
        </doc>
      </field>

      <field name = "no local" domain = "no local" />

      <field name = "no ack" domain = "no ack" />

      <field name = "exclusive" type = "bit">
        request exclusive access
        <doc>
          Request exclusive consumer access, meaning only this consumer can
          access the queue.
        </doc>
        <doc name = "rule" test = "amq_basic_02">
          If the server cannot grant exclusive access to the queue when asked,
          - because there are other consumers active - it MUST raise a channel
          exception with return code 403 (access refused).
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name = "consume-ok" synchronous = "1" index = "21">
      confirm a new consumer
      <doc>
        The server provides the client with a consumer tag, which is used by
        the client for methods called on the consumer at a later stage.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Holds the consumer tag specified by the client or provided by the
          server.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "cancel" synchronous = "1" index = "30">
      end a queue consumer
      <doc test = "amq_basic_04">
        This method cancels a consumer. This does not affect already delivered
        messages, but it does mean the server will not send any more messages
        for that consumer.  The client may receive an abitrary number of
        messages in between sending the cancel method and receiving the
        cancel-ok reply.
      </doc>
      <doc name = "rule" test = "todo">
        If the queue no longer exists when the client sends a cancel command,
        or the consumer has been cancelled for other reasons, this command has
        no effect.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "cancel-ok" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name = "cancel-ok" synchronous = "1" index = "31">
      confirm a cancelled consumer
      <doc>
        This method confirms that the cancellation was completed.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "publish" content = "1" index = "40">
      publish a message
      <doc>
        This method publishes a message to a specific exchange. The message
        will be routed to queues as defined by the exchange configuration and
        distributed to any active consumers when the transaction, if any, is
        committed.
      </doc>
      <chassis name = "server" implement = "MUST" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "write" access
          rights to the access realm for the exchange.
        </doc>
      </field>

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange to publish to.  The exchange name
          can be empty, meaning the default exchange.  If the exchange name is
          specified, and that exchange does not exist, the server will raise a
          channel exception.
        </doc>
        <doc name = "rule" test = "amq_basic_06">
          The server MUST accept a blank exchange name to mean the default
          exchange.
        </doc>
        <doc name = "rule" test = "amq_basic_14">
          If the exchange was declared as an internal exchange, the server MUST
          raise a channel exception with a reply code 403 (access refused).
        </doc>
        <doc name = "rule" test = "amq_basic_15">
          The exchange MAY refuse basic content in which case it MUST raise a
          channel exception with reply code 540 (not implemented).
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key for the message.  The routing key is used
          for routing messages depending on the exchange configuration.
        </doc>
      </field>

      <field name = "mandatory" type = "bit">
        indicate mandatory routing
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue.  If this flag is set, the server will return an
          unroutable message with a Return method.  If this flag is zero, the
          server silently drops the message.
        </doc>
        <doc name = "rule" test = "amq_basic_07">
          The server SHOULD implement the mandatory flag.
        </doc>
      </field>

      <field name = "immediate" type = "bit">
        request immediate delivery
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue consumer immediately.  If this flag is set, the
          server will return an undeliverable message with a Return method.  If
          this flag is zero, the server will queue the message, but with no
          guarantee that it will ever be consumed.
        </doc>
        <doc name = "rule" test = "amq_basic_16">
          The server SHOULD implement the immediate flag.
        </doc>
      </field>
    </method>

    <method name = "return" content = "1" index = "50">
      return a failed message
      <doc>
        This method returns an undeliverable message that was published with
        the "immediate" flag set, or an unroutable message published with the
        "mandatory" flag set. The reply code and text provide information about
        the reason that the message was undeliverable.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "reply code" domain = "reply code" />
      <field name = "reply text" domain = "reply text" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "deliver" content = "1" index = "60">
      notify the client of a consumer message
      <doc>
        This method delivers a message to the client, via a consumer.  In the
        asynchronous message delivery model, the client starts a consumer using
        the Consume method, then the server responds with Deliver methods as
        and when messages arrive for that consumer.
      </doc>
      <doc name = "rule" test = "amq_basic_19">
        The server SHOULD track the number of times a message has been
        delivered to clients and when a message is redelivered a certain number
        of times - e.g. 5 times - without being acknowledged, the server SHOULD
        consider the message to be unprocessable (possibly causing client
        applications to abort), and move the message to a dead letter queue.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "redelivered" domain = "redelivered" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "get" synchronous = "1" index = "70">
      direct access to a queue
      <doc>
        This method provides a direct access to the messages in a queue using a
        synchronous dialogue that is designed for specific types of application
        where synchronous functionality is more important than performance.
      </doc>
      <response name = "get-ok" />
      <response name = "get-empty" />
      <chassis name = "server" implement = "MUST" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "read" access
          rights to the realm for the queue.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to consume from.  If the queue name
          is null, refers to the current queue for the channel, which is the
          last declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
      </field>

      <field name = "no ack" domain = "no ack" />
    </method>

    <method name = "get-ok" synchronous = "1" content = "1" index = "71">
      provide client with a message
      <doc>
        This method delivers a message to the client following a get method.  A
        message delivered by 'get-ok' must be acknowledged unless the no-ack
        option was set in the get method.
      </doc>
      <chassis name = "client" implement = "MAY" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "redelivered"  domain = "redelivered"  />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.  If empty, the message was published to the default
          exchange.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>
      </field>

      <field name = "message count" type = "long" >
        number of messages pending
        <doc>
          This field reports the number of messages pending on the queue,
          excluding the message being delivered.  Note that this figure is
          indicative, not reliable, and can change arbitrarily as messages are
          added to the queue and removed by other clients.
        </doc>
      </field>
    </method>


    <method name = "get-empty" synchronous = "1" index = "72">
      indicate no messages available
      <doc>
        This method tells the client that the queue has no messages available
        for the client.
      </doc>
      <chassis name = "client" implement = "MAY" />

      <field name = "cluster id" type = "shortstr">
        Cluster id
        <doc>
          For use by cluster applications, should not be used by client
          applications.
        </doc>
      </field>
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "ack" index = "80">
      acknowledge one or more messages
      <doc>
        This method acknowledges one or more messages delivered via the Deliver
        or Get-Ok methods.  The client can ask to confirm a single message or a
        set of messages up to and including a specific message.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "multiple" type = "bit">
        acknowledge multiple messages
        <doc>
          If set to 1, the delivery tag is treated as "up to and including", so
          that the client can acknowledge multiple messages with a single
          method.  If set to zero, the delivery tag refers to a single message.
          If the multiple field is 1, and the delivery tag is zero, tells the
          server to acknowledge all outstanding mesages.
        </doc>
        <doc name = "rule" test = "amq_basic_20">
          The server MUST validate that a non-zero delivery-tag refers to an
          delivered message, and raise a channel exception if this is not the
          case.
        </doc>
      </field>
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "reject" index = "90">
      reject an incoming message
      <doc>
        This method allows a client to reject a message.  It can be used to
        interrupt and cancel large incoming messages, or return untreatable
        messages to their original queue.
      </doc>
      <doc name = "rule" test = "amq_basic_21">
        The server SHOULD be capable of accepting and process the Reject method
        while sending message content with a Deliver or Get-Ok method.  I.e.
        the server should read and process incoming methods while sending
        output frames.  To cancel a partially-send content, the server sends a
        content body frame of size 1 (i.e. with no data except the frame-end
        octet).
      </doc>
      <doc name = "rule" test = "amq_basic_22">
        The server SHOULD interpret this method as meaning that the client is
        unable to process the message at this time.
      </doc>
      <doc name = "rule">
        A client MUST NOT use this method as a means of selecting messages to
        process.  A rejected message MAY be discarded or dead-lettered, not
        necessarily passed to another client.
      </doc>      
      <chassis name = "server" implement = "MUST" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "requeue" type = "bit">
        requeue the message
        <doc>
          If this field is zero, the message will be discarded.  If this bit is
          1, the server will attempt to requeue the message.
        </doc>
        <doc name = "rule" test = "amq_basic_23">
          The server MUST NOT deliver the message to the same client within the
          context of the current channel.  The recommended strategy is to
          attempt to deliver the message to an alternative consumer, and if
          that is not possible, to move the message to a dead-letter queue.
          The server MAY use more sophisticated tracking to hold the message on
          the queue and redeliver it to the same client at a later stage.
        </doc>
      </field>
    </method>

    <method name = "recover" index = "100">
      redeliver unacknowledged messages. This method is only allowed on
      non-transacted channels.
      <doc>
        This method asks the broker to redeliver all unacknowledged messages on
        a specifieid channel. Zero or more messages may be redelivered.
      </doc>
      <chassis name = "server" implement = "MUST" />

      <field name = "requeue" type = "bit">
        requeue the message
        <doc>
          If this field is zero, the message will be redelivered to the
          original recipient.  If this bit is 1, the server will attempt to
          requeue the message, potentially then delivering it to an alternative
          subscriber.
        </doc>
      </field>

      <doc name="rule">
        The server MUST set the redelivered flag on all messages that are
        resent.
      </doc>
      <doc name="rule">
        The server MUST raise a channel exception if this is called on a
        transacted channel.
      </doc>
    </method>


  </class>


  <class name="file" handler="channel" index="70">
    <!--
    ======================================================
    ==      FILE TRANSFER
    ======================================================
    -->
    work with file content
    <doc>
      The file class provides methods that support reliable file transfer.
      File messages have a specific set of properties that are required for
      interoperability with file transfer applications. File messages and
      acknowledgements are subject to channel transactions.  Note that the file
      class does not provide message browsing methods; these are not compatible
      with the staging model.  Applications that need browsable file transfer
      should use Basic content and the Basic class.
    </doc>

    <doc name = "grammar">
      file                = C:QOS S:QOS-OK
                          / C:CONSUME S:CONSUME-OK
                          / C:CANCEL S:CANCEL-OK
                          / C:OPEN S:OPEN-OK C:STAGE content
                          / S:OPEN C:OPEN-OK S:STAGE content
                          / C:PUBLISH
                          / S:DELIVER
                          / S:RETURN
                          / C:ACK
                          / C:REJECT
    </doc>

    <chassis name = "server" implement = "MAY" />
    <chassis name = "client" implement = "MAY" />

    <doc name = "rule">
      The server MUST make a best-effort to hold file messages on a reliable
      storage mechanism.
    </doc>
    <doc name = "rule">
      The server MUST NOT discard a file message in case of a queue overflow.
      The server MUST use the Channel.Flow method to slow or stop a file
      message publisher when necessary.
    </doc>
    <doc name = "rule">
      The server MUST implement at least 2 priority levels for file messages,
      where priorities 0-4 and 5-9 are treated as two distinct levels. The
      server MAY implement up to 10 priority levels.
    </doc>
    <doc name = "rule">
      The server MUST support both automatic and explicit acknowledgements on
      file content.
    </doc>

    <!--  These are the properties for a File content  -->

    <field name = "content type" type = "shortstr">
      MIME content type
    </field>
    <field name = "content encoding" type = "shortstr">
      MIME content encoding
    </field>
    <field name = "headers" type = "table">
      Message header field table
    </field>
    <field name = "priority" type = "octet">
      The message priority, 0 to 9
    </field>
    <field name = "reply to" type = "shortstr">
      The destination to reply to
    </field>
    <field name = "message id" type = "shortstr">
      The application message identifier
    </field>
    <field name = "filename" type = "shortstr">
      The message filename
    </field>
    <field name = "timestamp" type = "timestamp">
      The message timestamp
    </field>
    <field name = "cluster id" type = "shortstr">
      Intra-cluster routing identifier
    </field>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "qos" synchronous = "1" index = "10">
      specify quality of service
      <doc>
        This method requests a specific quality of service.  The QoS can be
        specified for the current channel or for all channels on the
        connection.  The particular properties and semantics of a qos method
        always depend on the content class semantics.  Though the qos method
        could in principle apply to both peers, it is currently meaningful only
        for the server.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "qos-ok" />

      <field name = "prefetch size" type = "long">
        prefetch window in octets
        <doc>
          The client can request that messages be sent in advance so that when
          the client finishes processing a message, the following message is
          already held locally, rather than needing to be sent down the
          channel.  Prefetching gives a performance improvement.  This field
          specifies the prefetch window size in octets. May be set to zero,
          meaning "no specific limit".  Note that other prefetch limits may
          still apply. The prefetch-size is ignored if the no-ack option is
          set.
        </doc>
      </field>

      <field name = "prefetch count" type = "short">
        prefetch window in messages
        <doc>
          Specifies a prefetch window in terms of whole messages.  This is
          compatible with some file API implementations.  This field may be
          used in combination with the prefetch-size field; a message will only
          be sent in advance if both prefetch windows (and those at the channel
          and connection level) allow it.  The prefetch-count is ignored if the
          no-ack option is set.
        </doc>
        <doc name = "rule">
          The server MAY send less data in advance than allowed by the client's
          specified prefetch windows but it MUST NOT send more.
        </doc>
      </field>

      <field name = "global" type = "bit">
        apply to entire connection
        <doc>
          By default the QoS settings apply to the current channel only.  If
          this field is set, they are applied to the entire connection.
        </doc>
      </field>
    </method>

    <method name = "qos-ok" synchronous = "1" index = "11">
      confirm the requested qos
      <doc>
        This method tells the client that the requested QoS levels could be
        handled by the server.  The requested QoS applies to all active
        consumers until a new QoS is defined.
      </doc>
      <chassis name = "client" implement = "MUST" />
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "consume" synchronous = "1" index = "20">
      start a queue consumer
      <doc>
        This method asks the server to start a "consumer", which is a transient
        request for messages from a specific queue. Consumers last as long as
        the channel they were created on, or until the client cancels them.
      </doc>
      <doc name = "rule">
        The server SHOULD support at least 16 consumers per queue, unless the
        queue was declared as private, and ideally, impose no limit except as
        defined by available resources.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "consume-ok" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "read" access
          rights to the realm for the queue.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to consume from.  If the queue name
          is null, refers to the current queue for the channel, which is the
          last declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
      </field>

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Specifies the identifier for the consumer. The consumer tag is local
          to a connection, so two clients can use the same consumer tags. If
          this field is empty the server will generate a unique tag.
        </doc>
        <doc name = "rule" test = "todo">
          The tag MUST NOT refer to an existing consumer. If the client
          attempts to create two consumers with the same non-empty tag the
          server MUST raise a connection exception with reply code 530 (not
          allowed).
        </doc>
      </field>

      <field name = "no local" domain = "no local" />

      <field name = "no ack" domain = "no ack" />

      <field name = "exclusive" type = "bit">
        request exclusive access
        <doc>
          Request exclusive consumer access, meaning only this consumer can
          access the queue.
        </doc>
        <doc name = "rule" test = "amq_file_00">
          If the server cannot grant exclusive access to the queue when asked,
          - because there are other consumers active - it MUST raise a channel
          exception with return code 405 (resource locked).
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name = "consume-ok" synchronous = "1" index = "21">
      confirm a new consumer
      <doc>
        This method provides the client with a consumer tag which it MUST use
        in methods that work with the consumer.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Holds the consumer tag specified by the client or provided by the
          server.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "cancel" synchronous = "1" index = "30">
      end a queue consumer
      <doc>
        This method cancels a consumer. This does not affect already delivered
        messages, but it does mean the server will not send any more messages
        for that consumer.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "cancel-ok" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name = "cancel-ok" synchronous = "1" index = "31">
      confirm a cancelled consumer
      <doc>
        This method confirms that the cancellation was completed.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "open" synchronous = "1" index = "40">
      request to start staging
      <doc>
        This method requests permission to start staging a message.  Staging
        means sending the message into a temporary area at the recipient end
        and then delivering the message by referring to this temporary area.
        Staging is how the protocol handles partial file transfers - if a
        message is partially staged and the connection breaks, the next time
        the sender starts to stage it, it can restart from where it left off.
      </doc>
      <response name = "open-ok" />
      <chassis name = "server" implement = "MUST" />
      <chassis name = "client" implement = "MUST" />

      <field name = "identifier" type = "shortstr">
        staging identifier
        <doc>
          This is the staging identifier. This is an arbitrary string chosen by
          the sender.  For staging to work correctly the sender must use the
          same staging identifier when staging the same message a second time
          after recovery from a failure.  A good choice for the staging
          identifier would be the SHA1 hash of the message properties data
          (including the original filename, revised time, etc.).
        </doc>
      </field>

      <field name = "content size" type = "longlong">
        message content size
        <doc>
          The size of the content in octets.  The recipient may use this
          information to allocate or check available space in advance, to avoid
          "disk full" errors during staging of very large messages.
        </doc>
        <doc name = "rule">
          The sender MUST accurately fill the content-size field.  Zero-length
          content is permitted.
        </doc>
      </field>
    </method>

    <method name = "open-ok" synchronous = "1" index = "41">
      confirm staging ready
      <doc>
        This method confirms that the recipient is ready to accept staged data.
        If the message was already partially-staged at a previous time the
        recipient will report the number of octets already staged.
      </doc>
      <response name = "stage" />
      <chassis name = "server" implement = "MUST" />
      <chassis name = "client" implement = "MUST" />

      <field name = "staged size" type = "longlong">
        already staged amount
        <doc>
          The amount of previously-staged content in octets.  For a new message
          this will be zero.
        </doc>
        <doc name = "rule">
          The sender MUST start sending data from this octet offset in the
          message, counting from zero.
        </doc>
        <doc name = "rule">
          The recipient MAY decide how long to hold partially-staged content
          and MAY implement staging by always discarding partially-staged
          content.  However if it uses the file content type it MUST support
          the staging methods.
        </doc>
      </field>
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "stage" content = "1" index = "50">
      stage message content
      <doc>
        This method stages the message, sending the message content to the
        recipient from the octet offset specified in the Open-Ok method.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <chassis name = "client" implement = "MUST" />
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "publish" index = "60">
      publish a message
      <doc>
        This method publishes a staged file message to a specific exchange.
        The file message will be routed to queues as defined by the exchange
        configuration and distributed to any active consumers when the
        transaction, if any, is committed.
      </doc>
      <chassis name = "server" implement = "MUST" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "write" access
          rights to the access realm for the exchange.
        </doc>
      </field>

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange to publish to.  The exchange name
          can be empty, meaning the default exchange.  If the exchange name is
          specified, and that exchange does not exist, the server will raise a
          channel exception.
        </doc>
        <doc name = "rule">
          The server MUST accept a blank exchange name to mean the default
          exchange.
        </doc>
        <doc name = "rule">
          If the exchange was declared as an internal exchange, the server MUST
          respond with a reply code 403 (access refused) and raise a channel
          exception.
        </doc>
        <doc name = "rule">
          The exchange MAY refuse file content in which case it MUST respond
          with a reply code 540 (not implemented) and raise a channel
          exception.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key for the message.  The routing key is used
          for routing messages depending on the exchange configuration.
        </doc>
      </field>

      <field name = "mandatory" type = "bit">
        indicate mandatory routing
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue.  If this flag is set, the server will return an
          unroutable message with a Return method.  If this flag is zero, the
          server silently drops the message.
        </doc>
        <doc name = "rule" test = "amq_file_00">
          The server SHOULD implement the mandatory flag.
        </doc>
      </field>

      <field name = "immediate" type = "bit">
        request immediate delivery
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue consumer immediately.  If this flag is set, the
          server will return an undeliverable message with a Return method.  If
          this flag is zero, the server will queue the message, but with no
          guarantee that it will ever be consumed.
        </doc>
        <doc name = "rule" test = "amq_file_00">
          The server SHOULD implement the immediate flag.
        </doc>
      </field>

      <field name = "identifier" type = "shortstr">
        staging identifier
        <doc>
          This is the staging identifier of the message to publish.  The
          message must have been staged.  Note that a client can send the
          Publish method asynchronously without waiting for staging to finish.
        </doc>
      </field>
    </method>

    <method name = "return" content = "1" index = "70">
      return a failed message
      <doc>
        This method returns an undeliverable message that was published with
        the "immediate" flag set, or an unroutable message published with the
        "mandatory" flag set. The reply code and text provide information about
        the reason that the message was undeliverable.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "reply code" domain = "reply code" />
      <field name = "reply text" domain = "reply text" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "deliver" index = "80">
      notify the client of a consumer message
      <doc>
        This method delivers a staged file message to the client, via a
        consumer. In the asynchronous message delivery model, the client starts
        a consumer using the Consume method, then the server responds with
        Deliver methods as and when messages arrive for that consumer.
      </doc>
      <doc name = "rule">
        The server SHOULD track the number of times a message has been
        delivered to clients and when a message is redelivered a certain number
        of times - e.g. 5 times - without being acknowledged, the server SHOULD
        consider the message to be unprocessable (possibly causing client
        applications to abort), and move the message to a dead letter queue.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "redelivered" domain = "redelivered" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>
      </field>

      <field name = "identifier" type = "shortstr">
        staging identifier
        <doc>
          This is the staging identifier of the message to deliver.  The
          message must have been staged.  Note that a server can send the
          Deliver method asynchronously without waiting for staging to finish.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "ack" index = "90">
      acknowledge one or more messages
      <doc>
        This method acknowledges one or more messages delivered via the Deliver
        method.  The client can ask to confirm a single message or a set of
        messages up to and including a specific message.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "multiple" type = "bit">
        acknowledge multiple messages
        <doc>
          If set to 1, the delivery tag is treated as "up to and including", so
          that the client can acknowledge multiple messages with a single
          method.  If set to zero, the delivery tag refers to a single message.
          If the multiple field is 1, and the delivery tag is zero, tells the
          server to acknowledge all outstanding mesages.
        </doc>
        <doc name = "rule">
          The server MUST validate that a non-zero delivery-tag refers to an
          delivered message, and raise a channel exception if this is not the
          case.
        </doc>
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "reject" index = "100">
      reject an incoming message
      <doc>
        This method allows a client to reject a message.  It can be used to
        return untreatable messages to their original queue.  Note that file
        content is staged before delivery, so the client will not use this
        method to interrupt delivery of a large message.
      </doc>
      <doc name = "rule">
        The server SHOULD interpret this method as meaning that the client is
        unable to process the message at this time.
      </doc>
      <doc name = "rule">
        A client MUST NOT use this method as a means of selecting messages to
        process.  A rejected message MAY be discarded or dead-lettered, not
        necessarily passed to another client.
      </doc>
      <chassis name = "server" implement = "MUST" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "requeue" type = "bit">
        requeue the message
        <doc>
          If this field is zero, the message will be discarded.  If this bit is
          1, the server will attempt to requeue the message.
        </doc>
        <doc name = "rule">
          The server MUST NOT deliver the message to the same client within the
          context of the current channel.  The recommended strategy is to
          attempt to deliver the message to an alternative consumer, and if
          that is not possible, to move the message to a dead-letter queue.
          The server MAY use more sophisticated tracking to hold the message on
          the queue and redeliver it to the same client at a later stage.
        </doc>
      </field>
    </method>

  </class>

  <class name="stream" handler="channel" index="80">
    <!--
    ======================================================
    ==       STREAMING
    ======================================================
    -->
    work with streaming content

    <doc>
      The stream class provides methods that support multimedia streaming.  The
      stream class uses the following semantics: one message is one packet of
      data; delivery is unacknowleged and unreliable; the consumer can specify
      quality of service parameters that the server can try to adhere to;
      lower-priority messages may be discarded in favour of high priority
      messages.
    </doc>

    <doc name = "grammar">
      stream              = C:QOS S:QOS-OK
                          / C:CONSUME S:CONSUME-OK
                          / C:CANCEL S:CANCEL-OK
                          / C:PUBLISH content
                          / S:RETURN
                          / S:DELIVER content
    </doc>

    <chassis name = "server" implement = "MAY" />
    <chassis name = "client" implement = "MAY" />

    <doc name = "rule">
      The server SHOULD discard stream messages on a priority basis if the
      queue size exceeds some configured limit.
    </doc>
    <doc name = "rule">
      The server MUST implement at least 2 priority levels for stream messages,
      where priorities 0-4 and 5-9 are treated as two distinct levels. The
      server MAY implement up to 10 priority levels.
    </doc>
    <doc name = "rule">
      The server MUST implement automatic acknowledgements on stream content.
      That is, as soon as a message is delivered to a client via a Deliver
      method, the server must remove it from the queue.
    </doc>


    <!--  These are the properties for a Stream content  -->

    <field name = "content type" type = "shortstr">
      MIME content type
    </field>
    <field name = "content encoding" type = "shortstr">
      MIME content encoding
    </field>
    <field name = "headers" type = "table">
      Message header field table
    </field>
    <field name = "priority" type = "octet">
      The message priority, 0 to 9
    </field>
    <field name = "timestamp" type = "timestamp">
      The message timestamp
    </field>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "qos" synchronous = "1" index = "10">
      specify quality of service
      <doc>
        This method requests a specific quality of service.  The QoS can be
        specified for the current channel or for all channels on the
        connection.  The particular properties and semantics of a qos method
        always depend on the content class semantics.  Though the qos method
        could in principle apply to both peers, it is currently meaningful only
        for the server.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "qos-ok" />

      <field name = "prefetch size" type = "long">
        prefetch window in octets
        <doc>
          The client can request that messages be sent in advance so that when
          the client finishes processing a message, the following message is
          already held locally, rather than needing to be sent down the
          channel.  Prefetching gives a performance improvement.  This field
          specifies the prefetch window size in octets. May be set to zero,
          meaning "no specific limit".  Note that other prefetch limits may
          still apply.
        </doc>
      </field>

      <field name = "prefetch count" type = "short">
        prefetch window in messages
        <doc>
          Specifies a prefetch window in terms of whole messages.  This field
          may be used in combination with the prefetch-size field; a message
          will only be sent in advance if both prefetch windows (and those at
          the channel and connection level) allow it.
        </doc>
      </field>

      <field name = "consume rate" type = "long">
        transfer rate in octets/second
        <doc>
          Specifies a desired transfer rate in octets per second. This is
          usually determined by the application that uses the streaming data.
          A value of zero means "no limit", i.e. as rapidly as possible.
        </doc>
        <doc name = "rule">
          The server MAY ignore the prefetch values and consume rates,
          depending on the type of stream and the ability of the server to
          queue and/or reply it.  The server MAY drop low-priority messages in
          favour of high-priority messages.
        </doc>
      </field>

      <field name = "global" type = "bit">
        apply to entire connection
        <doc>
          By default the QoS settings apply to the current channel only.  If
          this field is set, they are applied to the entire connection.
        </doc>
      </field>
    </method>

    <method name = "qos-ok" synchronous = "1" index = "11">
      confirm the requested qos
      <doc>
        This method tells the client that the requested QoS levels could be
        handled by the server.  The requested QoS applies to all active
        consumers until a new QoS is defined.
      </doc>
      <chassis name = "client" implement = "MUST" />
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "consume" synchronous = "1" index = "20">
      start a queue consumer
      <doc>
        This method asks the server to start a "consumer", which is a transient
        request for messages from a specific queue. Consumers last as long as
        the channel they were created on, or until the client cancels them.
      </doc>
      <doc name = "rule">
        The server SHOULD support at least 16 consumers per queue, unless the
        queue was declared as private, and ideally, impose no limit except as
        defined by available resources.
      </doc>
      <doc name = "rule">
        Streaming applications SHOULD use different channels to select
        different streaming resolutions. AMQP makes no provision for filtering
        and/or transforming streams except on the basis of priority-based
        selective delivery of individual messages.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "consume-ok" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "read" access
          rights to the realm for the queue.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue to consume from.  If the queue name
          is null, refers to the current queue for the channel, which is the
          last declared queue.
        </doc>
        <doc name = "rule">
          If the client did not previously declare a queue, and the queue name
          in this method is empty, the server MUST raise a connection exception
          with reply code 530 (not allowed).
        </doc>
      </field>

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Specifies the identifier for the consumer. The consumer tag is local
          to a connection, so two clients can use the same consumer tags. If
          this field is empty the server will generate a unique tag.
        </doc>
        <doc name = "rule" test = "todo">
          The tag MUST NOT refer to an existing consumer. If the client
          attempts to create two consumers with the same non-empty tag the
          server MUST raise a connection exception with reply code 530 (not
          allowed).
        </doc>
      </field>

      <field name = "no local" domain = "no local" />

      <field name = "exclusive" type = "bit">
        request exclusive access
        <doc>
          Request exclusive consumer access, meaning only this consumer can
          access the queue.
        </doc>
        <doc name = "rule" test = "amq_file_00">
          If the server cannot grant exclusive access to the queue when asked,
          - because there are other consumers active - it MUST raise a channel
          exception with return code 405 (resource locked).
        </doc>
      </field>

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>


    <method name = "consume-ok" synchronous = "1" index = "21">
      confirm a new consumer
      <doc>
        This method provides the client with a consumer tag which it may use in
        methods that work with the consumer.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag">
        <doc>
          Holds the consumer tag specified by the client or provided by the
          server.
        </doc>
      </field>
    </method>

    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "cancel" synchronous = "1" index = "30">
      end a queue consumer
      <doc>
        This method cancels a consumer.  Since message delivery is asynchronous
        the client may continue to receive messages for a short while after
        canceling a consumer.  It may process or discard these as appropriate.
      </doc>
      <chassis name = "server" implement = "MUST" />
      <response name = "cancel-ok" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "nowait" type = "bit">
        do not send a reply method
        <doc>
          If set, the server will not respond to the method. The client should
          not wait for a reply method.  If the server could not complete the
          method it will raise a channel or connection exception.
        </doc>
      </field>
    </method>

    <method name = "cancel-ok" synchronous = "1" index = "31">
      confirm a cancelled consumer
      <doc>
        This method confirms that the cancellation was completed.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "publish" content = "1" index = "40">
      publish a message
      <doc>
        This method publishes a message to a specific exchange. The message
        will be routed to queues as defined by the exchange configuration and
        distributed to any active consumers as appropriate.
      </doc>
      <chassis name = "server" implement = "MUST" />

      <field name = "ticket" domain = "access ticket">
        <doc name = "rule">
          The client MUST provide a valid access ticket giving "write" access
          rights to the access realm for the exchange.
        </doc>
      </field>

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange to publish to.  The exchange name
          can be empty, meaning the default exchange.  If the exchange name is
          specified, and that exchange does not exist, the server will raise a
          channel exception.
        </doc>
        <doc name = "rule">
          The server MUST accept a blank exchange name to mean the default
          exchange.
        </doc>
        <doc name = "rule">
          If the exchange was declared as an internal exchange, the server MUST
          respond with a reply code 403 (access refused) and raise a channel
          exception.
        </doc>
        <doc name = "rule">
          The exchange MAY refuse stream content in which case it MUST respond
          with a reply code 540 (not implemented) and raise a channel
          exception.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key for the message.  The routing key is used
          for routing messages depending on the exchange configuration.
        </doc>
      </field>

      <field name = "mandatory" type = "bit">
        indicate mandatory routing
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue.  If this flag is set, the server will return an
          unroutable message with a Return method.  If this flag is zero, the
          server silently drops the message.
        </doc>
        <doc name = "rule" test = "amq_stream_00">
          The server SHOULD implement the mandatory flag.
        </doc>
      </field>

      <field name = "immediate" type = "bit">
        request immediate delivery
        <doc>
          This flag tells the server how to react if the message cannot be
          routed to a queue consumer immediately.  If this flag is set, the
          server will return an undeliverable message with a Return method.  If
          this flag is zero, the server will queue the message, but with no
          guarantee that it will ever be consumed.
        </doc>
        <doc name = "rule" test = "amq_stream_00">
          The server SHOULD implement the immediate flag.
        </doc>
      </field>
    </method>

    <method name = "return" content = "1" index = "50">
      return a failed message
      <doc>
        This method returns an undeliverable message that was published with
        the "immediate" flag set, or an unroutable message published with the
        "mandatory" flag set. The reply code and text provide information about
        the reason that the message was undeliverable.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "reply code" domain = "reply code" />
      <field name = "reply text" domain = "reply text" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "routing key" type = "shortstr">
        Message routing key
        <doc>
          Specifies the routing key name specified when the message was
          published.
        </doc>     
      </field>
    </method>


    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->

    <method name = "deliver" content = "1" index = "60">
      notify the client of a consumer message
      <doc>
        This method delivers a message to the client, via a consumer.  In the
        asynchronous message delivery model, the client starts a consumer using
        the Consume method, then the server responds with Deliver methods as
        and when messages arrive for that consumer.
      </doc>
      <chassis name = "client" implement = "MUST" />

      <field name = "consumer tag" domain = "consumer tag" />

      <field name = "delivery tag" domain = "delivery tag" />

      <field name = "exchange" domain = "exchange name">
        <doc>
          Specifies the name of the exchange that the message was originally
          published to.
        </doc>
      </field>

      <field name = "queue" domain = "queue name">
        <doc>
          Specifies the name of the queue that the message came from. Note that
          a single channel can start many consumers on different queues.
        </doc>
        <assert check = "notnull" />
      </field>
    </method>
  </class>

  <class name="tx" handler="channel" index="90">
    <!--
    ======================================================
    ==       TRANSACTIONS
    ======================================================
    -->
    work with standard transactions

    <doc>
      Standard transactions provide so-called "1.5 phase commit".  We can
      ensure that work is never lost, but there is a chance of confirmations
      being lost, so that messages may be resent.  Applications that use
      standard transactions must be able to detect and ignore duplicate
      messages.
    </doc>
    <rule implement="SHOULD">
      An client using standard transactions SHOULD be able to track all
      messages received within a reasonable period, and thus detect and reject
      duplicates of the same message. It SHOULD NOT pass these to the
      application layer.
    </rule>
    <doc name="grammar">
      tx                  = C:SELECT S:SELECT-OK
                          / C:COMMIT S:COMMIT-OK
                          / C:ROLLBACK S:ROLLBACK-OK
    </doc>
    <chassis name="server" implement="SHOULD"/>
    <chassis name="client" implement="MAY"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="select" synchronous="1" index="10">
      select standard transaction mode
      <doc>
        This method sets the channel to use standard transactions.  The client
        must use this method at least once on a channel before using the Commit
        or Rollback methods.
      </doc>
      <chassis name="server" implement="MUST"/>
      <response name="select-ok"/>
    </method>
    <method name="select-ok" synchronous="1" index="11">
      confirm transaction mode
      <doc>
        This method confirms to the client that the channel was successfully
        set to use standard transactions.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="commit" synchronous="1" index="20">
      commit the current transaction
      <doc>
        This method commits all messages published and acknowledged in the
        current transaction.  A new transaction starts immediately after a
        commit.
      </doc>
      <chassis name="server" implement="MUST"/>
      <response name="commit-ok"/>
    </method>
    <method name="commit-ok" synchronous="1" index="21">
      confirm a successful commit
      <doc>
        This method confirms to the client that the commit succeeded.  Note
        that if a commit fails, the server raises a channel exception.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="rollback" synchronous="1" index="30">
      abandon the current transaction
      <doc>
        This method abandons all messages published and acknowledged in the
        current transaction.  A new transaction starts immediately after a
        rollback.
      </doc>
      <chassis name="server" implement="MUST"/>
      <response name="rollback-ok"/>
    </method>
    <method name="rollback-ok" synchronous="1" index="31">
      confirm a successful rollback
      <doc>
        This method confirms to the client that the rollback succeeded.  Note
        that if an rollback fails, the server raises a channel exception.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
  </class>
  <class name="dtx" handler="channel" index="100">
    <!--
    ======================================================
    ==       DISTRIBUTED TRANSACTIONS
    ======================================================
    -->
    work with distributed transactions

    <doc>
      Distributed transactions provide so-called "2-phase commit".    The AMQP
      distributed transaction model supports the X-Open XA architecture and
      other distributed transaction implementations.  The Dtx class assumes
      that the server has a private communications channel (not AMQP) to a
      distributed transaction coordinator.
    </doc>
    <doc name="grammar">
      dtx                 = C:SELECT S:SELECT-OK
                          C:START S:START-OK
    </doc>
    <chassis name="server" implement="MAY"/>
    <chassis name="client" implement="MAY"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="select" synchronous="1" index="10">
      select standard transaction mode
      <doc>
        This method sets the channel to use distributed transactions.  The
        client must use this method at least once on a channel before using the
        Start method.
      </doc>
      <chassis name="server" implement="MUST"/>
      <response name="select-ok"/>
    </method>
    <method name="select-ok" synchronous="1" index="11">
      confirm transaction mode
      <doc>
        This method confirms to the client that the channel was successfully
        set to use distributed transactions.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="start" synchronous="1" index="20">
      start a new distributed transaction
      <doc>
        This method starts a new distributed transaction.  This must be the
        first method on a new channel that uses the distributed transaction
        mode, before any methods that publish or consume messages.
      </doc>
      <chassis name="server" implement="MAY"/>
      <response name="start-ok"/>
      <field name="dtx identifier" type="shortstr">
        transaction identifier
        <doc>
          The distributed transaction key. This identifies the transaction so
          that the AMQP server can coordinate with the distributed transaction
          coordinator.
        </doc>
        <assert check="notnull"/>
      </field>
    </method>
    <method name="start-ok" synchronous="1" index="21">
      confirm the start of a new distributed transaction
      <doc>
        This method confirms to the client that the transaction started.  Note
        that if a start fails, the server raises a channel exception.
      </doc>
      <chassis name="client" implement="MUST"/>
    </method>
  </class>
  <class name="tunnel" handler="tunnel" index="110">
    <!--
    ======================================================
    ==       TUNNEL
    ======================================================
    -->
    methods for protocol tunneling.

    <doc>
      The tunnel methods are used to send blocks of binary data - which can be
      serialised AMQP methods or other protocol frames - between AMQP peers.
    </doc>
    <doc name="grammar">
      tunnel              = C:REQUEST
                          / S:REQUEST
    </doc>
    <chassis name="server" implement="MAY"/>
    <chassis name="client" implement="MAY"/>
    <field name="headers" type="table">
      Message header field table
    </field>
    <field name="proxy name" type="shortstr">
      The identity of the tunnelling proxy
    </field>
    <field name="data name" type="shortstr">
      The name or type of the message being tunnelled
    </field>
    <field name="durable" type="octet">
      The message durability indicator
    </field>
    <field name="broadcast" type="octet">
      The message broadcast mode
    </field>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="request" content="1" index="10">
      sends a tunnelled method
      <doc>
        This method tunnels a block of binary data, which can be an encoded
        AMQP method or other data.  The binary data is sent as the content for
        the Tunnel.Request method.
      </doc>
      <chassis name="server" implement="MUST"/>
      <field name="meta data" type="table">
        meta data for the tunnelled block
        <doc>
          This field table holds arbitrary meta-data that the sender needs to
          pass to the recipient.
        </doc>
      </field>
    </method>
  </class>
  <class name="test" handler="channel" index="120">
    <!--
    ======================================================
    ==       TEST - CHECK FUNCTIONAL CAPABILITIES OF AN IMPLEMENTATION
    ======================================================
    -->
    test functional primitives of the implementation

    <doc>
      The test class provides methods for a peer to test the basic operational
      correctness of another peer. The test methods are intended to ensure that
      all peers respect at least the basic elements of the protocol, such as
      frame and content organisation and field types. We assume that a
      specially-designed peer, a "monitor client" would perform such tests.
    </doc>
    <doc name="grammar">
      test                = C:INTEGER S:INTEGER-OK
                          / S:INTEGER C:INTEGER-OK
                          / C:STRING S:STRING-OK
                          / S:STRING C:STRING-OK
                          / C:TABLE S:TABLE-OK
                          / S:TABLE C:TABLE-OK
                          / C:CONTENT S:CONTENT-OK
                          / S:CONTENT C:CONTENT-OK
    </doc>
    <chassis name="server" implement="MUST"/>
    <chassis name="client" implement="SHOULD"/>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="integer" synchronous="1" index="10">
      test integer handling
      <doc>
        This method tests the peer's capability to correctly marshal integer
        data.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="integer-ok"/>
      <field name="integer 1" type="octet">
        octet test value
        <doc>
          An octet integer test value.
        </doc>
      </field>
      <field name="integer 2" type="short">
        short test value
        <doc>
          A short integer test value.
        </doc>
      </field>
      <field name="integer 3" type="long">
        long test value
        <doc>
          A long integer test value.
        </doc>
      </field>
      <field name="integer 4" type="longlong">
        long-long test value
        <doc>
          A long long integer test value.
        </doc>
      </field>
      <field name="operation" type="octet">
        operation to test
        <doc>
          The client must execute this operation on the provided integer test
          fields and return the result.
        </doc>
        <assert check="enum">
          <value name="add">return sum of test values</value>
          <value name="min">return lowest of test values</value>
          <value name="max">return highest of test values</value>
        </assert>
      </field>
    </method>
    <method name="integer-ok" synchronous="1" index="11">
      report integer test result
      <doc>
        This method reports the result of an Integer method.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <field name="result" type="longlong">
        result value
        <doc>
          The result of the tested operation.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="string" synchronous="1" index="20">
      test string handling
      <doc>
        This method tests the peer's capability to correctly marshal string
        data.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="string-ok"/>
      <field name="string 1" type="shortstr">
        short string test value
        <doc>
          An short string test value.
        </doc>
      </field>
      <field name="string 2" type="longstr">
        long string test value
        <doc>
          A long string test value.
        </doc>
      </field>
      <field name="operation" type="octet">
        operation to test
        <doc>
          The client must execute this operation on the provided string test
          fields and return the result.
        </doc>
        <assert check="enum">
          <value name="add">return concatentation of test strings</value>
          <value name="min">return shortest of test strings</value>
          <value name="max">return longest of test strings</value>
        </assert>
      </field>
    </method>
    <method name="string-ok" synchronous="1" index="21">
      report string test result
      <doc>
        This method reports the result of a String method.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <field name="result" type="longstr">
        result value
        <doc>
          The result of the tested operation.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="table" synchronous="1" index="30">
      test field table handling
      <doc>
        This method tests the peer's capability to correctly marshal field
        table data.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="table-ok"/>
      <field name="table" type="table">
        field table of test values
        <doc>
          A field table of test values.
        </doc>
      </field>
      <field name="integer op" type="octet">
        operation to test on integers
        <doc>
          The client must execute this operation on the provided field table
          integer values and return the result.
        </doc>
        <assert check="enum">
          <value name="add">return sum of numeric field values</value>
          <value name="min">return min of numeric field values</value>
          <value name="max">return max of numeric field values</value>
        </assert>
      </field>
      <field name="string op" type="octet">
        operation to test on strings
        <doc>
          The client must execute this operation on the provided field table
          string values and return the result.
        </doc>
        <assert check="enum">
          <value name="add">return concatenation of string field values</value>
          <value name="min">return shortest of string field values</value>
          <value name="max">return longest of string field values</value>
        </assert>
      </field>
    </method>
    <method name="table-ok" synchronous="1" index="31">
      report table test result
      <doc>
        This method reports the result of a Table method.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <field name="integer result" type="longlong">
        integer result value
        <doc>
          The result of the tested integer operation.
        </doc>
      </field>
      <field name="string result" type="longstr">
        string result value
        <doc>
          The result of the tested string operation.
        </doc>
      </field>
    </method>
    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
    <method name="content" synchronous="1" content="1" index="40">
      test content handling
      <doc>
        This method tests the peer's capability to correctly marshal content.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <response name="content-ok"/>
    </method>
    <method name="content-ok" synchronous="1" content="1" index="41">
      report content test result
      <doc>
        This method reports the result of a Content method.  It contains the
        content checksum and echoes the original content as provided.
      </doc>
      <chassis name="client" implement="MUST"/>
      <chassis name="server" implement="MUST"/>
      <field name="content checksum" type="long">
        content hash
        <doc>
          The 32-bit checksum of the content, calculated by adding the content
          into a 32-bit accumulator.
        </doc>
      </field>
    </method>
  </class>
</amqp>