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
|
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
<!-- lifted from troff+ms+XMan by doclifter -->
<book id="SMlib">
<bookinfo>
<title>X Session Management Library</title>
<subtitle>X Consortium Standard</subtitle>
<releaseinfo>X Version 11, Release 6.4</releaseinfo>
<authorgroup>
<author>
<firstname>Ralph</firstname><surname>Mor</surname>
</author>
</authorgroup>
<corpname>X Consortium Standard</corpname>
<copyright>
<year>1993</year><year>1994</year>
<holder>X Consortium</holder>
</copyright>
<releaseinfo>Version 1.0</releaseinfo>
<affiliation><orgname>X Consortium</orgname></affiliation>
<productnumber>X Version 11, Release 7</productnumber>
<legalnotice>
<para>
Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
</para>
<para>
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
</para>
<para>
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF
ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
AND NONINFRINGEMENT. IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
</para>
<para>
Except as contained in this notice, the name of the X Consortium shall
not be used in advertising or otherwise to promote the sale, use or
other dealings in this Software without prior written authorization
from the X Consortium.
</para>
<para>
X Window System is a trademark of The Open Group.
</para>
</legalnotice>
</bookinfo>
<chapter id="overview_of_session_management">
<title>Overview of Session Management</title>
<abstract>
<para>
The purpose of the X Session Management Protocol (<acronym>XSMP</acronym>)
is to provide a uniform mechanism for users to save and restore their
sessions. A <firstterm>session</firstterm> is a group of clients,
each of which has a particular state. The session is controlled by a
network service called the <firstterm>session manager</firstterm>.
The session manager issues commands to its clients on behalf of the
user. These commands may cause clients to save their state or to
terminate. It is expected that the client will save its state in such
a way that the client can be restarted at a later time and resume its
operation as if it had never been terminated. A client's state might
include information about the file currently being edited, the current
position of the insertion point within the file, or the start of an
uncommitted transaction. The means by which clients are restarted is
unspecified by this protocol.
</para>
<para>
For purposes of this protocol, a <firstterm>client</firstterm> of the
session manager is defined as a connection to the session manager. A
client is typically, though not necessarily, a process running an
application program connected to an X display. However, a client may
be connected to more than one X display or not be connected to any X
displays at all.
</para>
</abstract>
</chapter>
<chapter id='the_session_management_library'>
<title>The Session Management Library</title>
<abstract>
<para>
The Session Management Library (<abbrev>SMlib</abbrev>) is a low-level
"C" language interface to XSMP. It is expected that higher level
toolkits, such as Xt, will hide many of the details of session
management from clients. Higher level toolkits might also be developed
for session managers to use, but no such effort is currently under way.
</para>
</abstract>
<para>
SMlib has two parts to it:
<itemizedlist mark='bullet'>
<listitem><para>One set of functions for clients that want to be part of a session</para></listitem>
<listitem><para>One set of functions for session managers to call</para></listitem>
</itemizedlist>
</para>
<para>
Some applications will use both sets of functions and act as
<firstterm>nested session managers</firstterm>. That is, they will be
both a session manager and a client of another session. An example is
a mail program that could start a text editor for editing the text of
a mail message. The mail program is part of a regular session and, at
the same time, is also acting as a session manager to the editor.
</para>
<para>
Clients initialize by connecting to the session manager and obtaining
a <firstterm>client-ID</firstterm> that uniquely identifies them in
the session. The session manager maintains a list of properties for
each client in the session. These properties describe the client's
environment and, most importantly, describe how the client can be
restarted (via an <property>SmRestartCommand</property>). Clients are
expected to save their state in such a way as to allow multiple
instantiations of themselves to be managed independently. For
example, clients may use their client-ID as part of a filename in
which to store the state for a particular instantiation. The
client-ID should be saved as part of the <property>SmRestartCommand</property>
so that the client will retain the same ID after it is restarted.
</para>
<para>
Once the client initializes itself with the session manager, it must
be ready to respond to messages from the session manager. For
example, it might be asked to save its state or to terminate. In the
case of a shutdown, the session manager might give each client a
chance to interact with the user and cancel the shutdown.
</para>
</chapter>
<chapter id='understanding_smlibs_dependence_on_ice'>
<title>Understanding SMlib's Dependence on ICE</title>
<para>
The X Session Management Protocol is layered on top of the
Inter-Client Exchange (<acronym>ICE</acronym>) Protocol. The ICE
protocol is designed to multiplex several protocols over a single
connection. As a result, working with SMlib requires a little
knowledge of how the ICE library works.
</para>
<para>
The ICE library utilizes callbacks to process messages. When a client
detects that there is data to read on an ICE connection, it should
call the <function>IceProcessMessages</function> function.
<function>IceProcessMessages</function> will read the message header
and look at the major opcode in order to determine which protocol the
message was intended for. The appropriate protocol library will then
be triggered to unpack the message and hand it off to the client via a
callback.
</para>
<para>
The main point to be aware of is that an application using SMlib must
have some code that detects when there is data to read on an ICE
connection. This can be done via a <function>select</function> call
on the file descriptor for the ICE connection, but more
typically, <function>XtAppAddInput</function> will be used to register
a callback that will invoke <function>IceProcessMessages</function>
each time there is data to read on the ICE connection.
</para>
<para>
To further complicate things, knowing which file descriptors to
call <function>select</function> on requires an understanding of how
ICE connections are created. On the client side, a call must be made
to <function>SmcOpenConnection</function> in order to open a connection
with a session manager. <function>SmcOpenConnection</function> will
internally makea call into <function>IceOpenConnection</function>
which will, in turn, determine if an ICE connection already exists
between the client and session manager. Most likely, a connection
will not already exist and a new ICE connection will be created. The
main point to be aware of is that, on the client side, it is not
obvious when ICE connections get created or destroyed, because
connections are shared when possible. To deal with this, the ICE
library lets the application register watch procedures that will be
invoked each time an ICE connection is opened or closed. These watch
procedures could be used to add or remove ICE file descriptors from
the list of descriptors to call <function>select</function> on.
</para>
<para>
On the session manager side, things work a bit differently. The
session manager has complete control over the creation of ICE
connections. The session manager has to first
call <function>IceListenForConnections</function> in order to start
listening for connections from clients. Once a connection attempt is
detected, <function>IceAcceptConnection</function> must be called, and
the session manager can simply add the new ICE file descriptor to the
list of descriptors to call <function>select</function> on.
</para>
<para>
For further information on the library functions related to ICE connections,
see the <citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</chapter>
<chapter id='header_files_and_library_name'>
<title>Header Files and Library Name</title>
<para>
Applications (both session managers and clients) should include the
header file <<filename class='headerfile'>X11/SM/SMlib.h</filename>>.
This header file defines all of the SMlib data structures and function
prototypes. <filename class='headerfile'>SMlib.h</filename> includes the
header file <<filename class='headerfile'>X11/SM/SM.h</filename>>,
which defines all of the SMlib constants.
</para>
<para>
Because SMlib is dependent on ICE, applications should link against
SMlib and ICElib by using
<quote><option>-lSM</option> <option>-lICE</option></quote>.
</para>
</chapter>
<chapter id='session_management_client'>
<title>Session Management Client (<acronym>Smc</acronym>) Functions</title>
<para>
This section discusses how Session Management clients:
<itemizedlist mark='bullet'>
<listitem><para>Connect to the Session Manager</para></listitem>
<listitem><para>Close the connection</para></listitem>
<listitem><para>Modify callbacks</para></listitem>
<listitem><para>Set, delete, and retrieve Session Manager properties</para></listitem>
<listitem><para>Interact with the user</para></listitem>
<listitem><para>Request a “Save Yourself”</para></listitem>
<listitem><para>Request a “Save Yourself Phase 2”</para></listitem>
<listitem><para>Complete a “Save Yourself”</para></listitem>
<listitem><para>Use Smc informational functions</para></listitem>
<listitem><para>Handle Errors</para></listitem>
</itemizedlist>
</para>
<sect1 id='connecting_to_the_session_manager'>
<title>Connecting to the Session Manager</title>
<para>
To open a connection with a session manager,
use <function>SmcOpenConnection</function>
</para>
<funcsynopsis id='smcopenconnection'>
<funcprototype>
<funcdef>SmcConn <function>SmcOpenConnection</function></funcdef>
<paramdef>char *<parameter>network_ids_list</parameter></paramdef>
<paramdef>SmPointer <parameter>context</parameter></paramdef>
<paramdef>int <parameter>xsmp_major_rev</parameter></paramdef>
<paramdef>int <parameter>xsmp_minor_rev</parameter></paramdef>
<paramdef>unsigned long <parameter>mask</parameter></paramdef>
<paramdef>SmcCallbacks *<parameter>callbacks</parameter></paramdef>
<paramdef>char *<parameter>previous_id</parameter></paramdef>
<paramdef>char **<parameter>client_id_ret</parameter></paramdef>
<paramdef>int <parameter>error_length</parameter></paramdef>
<paramdef>char *<parameter>error_string_ret</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>network_ids_list</parameter></term>
<listitem><para>Specifies the network ID(s) of the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>context</parameter></term>
<listitem><para>
A pointer to an opaque object or <constant>NULL</constant>. Used to determine
if an ICE connection can be shared
(see <link linkend='context_sharing'>below</link>).
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>xsmp_major_rev</parameter></term>
<listitem><para>
The highest major version of the XSMP the application supports.
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>xsmp_minor_rev</parameter></term>
<listitem><para>
The highest minor version of the XSMP the application supports (for
the specified <parameter>xsmp_major_rev</parameter>).
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>mask</parameter></term>
<listitem><para>A mask indicating which callbacks to register.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>callbacks</parameter></term>
<listitem><para>
The callbacks to register. These callbacks are used to respond to
messages from the session manager.
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>previous_id</parameter></term>
<listitem><para>The client ID from the previous session.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_id_ret</parameter></term>
<listitem><para>The client ID for the current session is returned.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_length</parameter></term>
<listitem><para>Length of the <parameter>error_string_ret</parameter> argument passed in.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_string_ret</parameter></term>
<listitem><para>
Returns a null-terminated error message, if any.
The <parameter>error_string_ret</parameter> argument points to user supplied
memory. No more than <parameter>error_length</parameter> bytes are used.
</para></listitem>
</varlistentry>
</variablelist>
<para>
The <parameter>network_ids_list</parameter> argument is a
null-terminated string containing a list of network IDs for the session
manager, separated by commas. If <parameter>network_ids_list</parameter>
is <constant>NULL</constant>, the value of
the <envar>SESSION_MANAGER</envar> environment variable will be used.
Each network ID has the following format:
<informaltable pgwide='0' frame='none'>
<tgroup cols='3' align='center'>
<colspec colname='c1'/>
<colspec colname='c2'/>
<colspec colname='c3'/>
<tbody>
<row>
<entry align='left'></entry>
<entry align='left'><literal>tcp/</literal><parameter><hostname></parameter><literal>:</literal><parameter><portnumber></parameter></entry>
<entry align='left'>or</entry>
</row>
<row>
<entry align='left'></entry>
<entry align='left'><literal>decnet/</literal><parameter><hostname></parameter><literal>::</literal><parameter><objname></parameter></entry>
<entry align='left'>or</entry>
</row>
<row>
<entry align='left'></entry>
<entry align='left'><literal>local/</literal><parameter><hostname></parameter><literal>:</literal><parameter><path></parameter></entry>
<entry align='left'></entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
<para>
An attempt will be made to use the first network ID. If that fails,
an attempt will be made using the second network ID, and so on.
</para>
<para>
After the connection is established, <function>SmcOpenConnection</function>
registers the client with the session manager. If the client is being
restarted from a previous session, <parameter>previous_id</parameter>
should contain a null terminated string representing the client ID from the
previous session. If the client is first joining the session,
<parameter>previous_id</parameter> should be set to <constant>NULL</constant>.
If <parameter>previous_id</parameter> is specified but is determined
to be invalid by the session manager, SMlib will re-register the
client with <parameter>previous_id</parameter> set to <constant>NULL</constant>.
</para>
<para>
If <function>SmcOpenConnection</function> succeeds, it returns an
opaque connection pointer of type <function>SmcConn</function> and the
<parameter>client_id_ret</parameter> argument contains the client ID to be
used for this session. The <parameter>client_id_ret</parameter> should be
freed with a call to <function>free</function> when no longer needed. On
failure, <function>SmcOpenConnection</function> returns
<constant>NULL</constant>, and the reason for failure is returned in
<parameter>error_string_ret</parameter>.
</para>
<para>
Note that SMlib uses the ICE protocol to establish a connection with
the session manager. If an ICE connection already exists between the
client and session manager, it might be possible for the same ICE
connection to be used for session management.
</para>
<para id='context_sharing'>
The context argument indicates how willing the client is to share the
ICE connection with other protocols. If context is <constant>NULL</constant>,
then the caller is always willing to share the connection. If context is not
<constant>NULL</constant>, then the caller is not willing to use a previously
opened ICE connection that has a different non-<constant>NULL</constant>
context associated with it.
</para>
<para>
As previously discussed
(<link linkend='understanding_smlibs_dependence_on_ice'>section 3,
“Understanding SMlib's Dependence on ICE”</link>), the
client will have to keep track of when ICE connections are created or
destroyed (using <function>IceAddConnectionWatch</function>
and <function>IceRemoveConnectionWatch</function> and will have to
call <function>IceProcessMessages</function> each time
a <function>select</function> shows that there is data to read on an
ICE connection. For further information, see the
<citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
<para>
The callbacks argument contains a set of callbacks used to respond to
session manager events. The mask argument specifies which callbacks
are set. All of the callbacks specified in this version of SMlib are
mandatory. The mask argument is necessary in order to maintain
backwards compatibility in future versions of the library.
</para>
<para>
The following values may be ORed together to obtain a
<parameter>mask</parameter> value:
<simplelist type='vert'>
<member><constant>SmcSaveYourselfProcMask</constant></member>
<member><constant>SmcDieProcMask</constant></member>
<member><constant>SmcSaveCompleteProcMask</constant></member>
<member><constant>SmcShutdownCancelledProcMask</constant></member>
</simplelist>
</para>
<para>
For each callback, the client can register a pointer to client data.
When SMlib invokes the callback, it will pass the client data pointer.
</para>
<!-- .ne 4 IGNORED -->
<synopsis>
typedef struct {
struct {
SmcSaveYourselfProc callback;
SmPointer client_data;
} save_yourself;
struct {
SmcDieProc callback;
SmPointer client_data;
} die;
struct {
SmcSaveCompleteProc callback;
SmPointer client_data;
} save_complete;
struct {
SmcShutdownCancelledProc callback;
SmPointer client_data;
} shutdown_cancelled;
} SmcCallbacks;
</synopsis>
<sect2 id='the_save_yourself_callback'>
<title>The Save Yourself Callback</title>
<para>
The Save Yourself callback is of type <function>SmcSaveYourselfProc</function>
</para>
<funcsynopsis id='saveyourselfproc'>
<funcprototype>
<funcdef>typedef void (*<function>SaveYourselfProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmcConn <parameter>client_data</parameter></paramdef>
<paramdef>int <parameter>save_type</parameter></paramdef>
<paramdef>Bool <parameter>shutdown</parameter></paramdef>
<paramdef>int <parameter>interact_style</parameter></paramdef>
<paramdef>Bool <parameter>fast</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>Client data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>save_type</parameter></term>
<listitem><para>Specifies the type of information that should be saved.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>shut_down</parameter></term>
<listitem><para>Specifies if a shutdown is taking place.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>interact_style</parameter></term>
<listitem><para>The type of interaction allowed with the user.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>fast</parameter></term>
<listitem><para>if <symbol>True</symbol>, then client should save its state as quickly as possible.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends a “Save Yourself” message to a
client either to checkpoint it or just before termination so that it
can save its state. The client responds with zero or more calls
to <function>SmcSetProperties</function> to update the properties
indicating how to restart the client. When all the properties have
been set, the client calls <function>SmcSaveYourselfDone</function>
</para>
<para>
If <parameter>interact_style</parameter> is
<constant>SmInteractStyleNone</constant> the
client must not interact with the user while saving state.
If <parameter>interact_style</parameter> is
<constant>SmInteractStyleErrors</constant> the
client may interact with the user only if an error condition arises.
If <parameter>interact_style</parameter> is
<constant>SmInteractStyleAny</constant> then the
client may interact with the user for any purpose. Because only one
client can interact with the user at a time, the client must
call <function>SmcInteractRequest</function> and wait for an
“Interact” message from the session manager. When the
client is done interacting with the user, it
calls <function>SmcInteractDone</function> The client may only
call <function>SmcInteractRequest</function> after it receives a
“Save Yourself” message and before it
calls <function>SmcSaveYourselfDone</function>
</para>
<para>
If <parameter>save_type</parameter> is <constant>SmSaveLocal</constant> the
client must update the properties to reflect its current state. Specifically,
it should save enough information to restore the state as seen by the
user of this client. It should not affect the state as seen by other users.
If <parameter>save_type</parameter> is <constant>SmSaveGlobal</constant>
the user wants the client to commit all of its data to permanent, globally
accessible storage.
If <parameter>save_type</parameter> is <constant>SmSaveBoth</constant>
the client should do both of these (it should first commit the data to
permanent storage before updating its properties).
</para>
<para>
Some examples are as follows:
<itemizedlist mark='bullet'>
<listitem><para>
If a word processor were sent a “Save Yourself” with a
type of <constant>SmSaveLocal</constant> it could create a temporary
file that included the current contents of the file, the location of
the cursor, and other aspects of the current editing session. It
would then update its <property>SmRestartCommand</property> property with
enough information to find this temporary file.
</para></listitem>
<listitem><para>
If a word processor were sent a “Save Yourself” with a
type of <constant>SmSaveGlobal</constant> it would simply save the
currently edited file.
</para></listitem>
<listitem><para>
If a word processor were sent a “Save Yourself” with a
type of <constant>SmSaveBoth</constant> it would first save the
currently edited file. It would then create a temporary file with
information such as the current position of the cursor and what file
is being edited. Finally, it would update its
<property>SmRestartCommand</property> property with enough information
to find the temporary file.
</para></listitem>
</itemizedlist>
</para>
<para>
The <parameter>shutdown</parameter> argument specifies whether the
system is being shut down.
The interaction is different depending on whether or not shutdown is
set. If not shutting down, the client should save its state and wait
for a “Save Complete” message. If shutting down, the
client must save state and then prevent interaction until it receives
either a “Die” or a “Shutdown Cancelled.”
</para>
<para>
The <parameter>fast</parameter> argument specifies that the client
should save its state as quickly as possible. For example, if the
session manager knows that power is about to fail, it would
set <parameter>fast</parameter> to <constant>True</constant>.
</para>
</sect2>
<sect2 id='the_die_callback'>
<title>The Die Callback</title>
<para>
The Die callback is of type <function>SmcDieProc</function>
</para>
<funcsynopsis id='smcdieproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmcDieProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmcConn <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>Client data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends a “Die” message to a client when
it wants it to die. The client should respond by calling
<function>SmcCloseConnection</function>. A session manager that
behaves properly will send a “Save Yourself” message
before the “Die” message.
</para>
</sect2>
<sect2 id='the_save_complete_callback'>
<title>The Save Complete Callback</title>
<para>
The Save Complete callback is of type <function>SmcSaveCompleteProc</function>
</para>
<funcsynopsis id='smcsavecompleteproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmcSaveCompleteProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>Client data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
</sect2>
<sect2 id='the_shutdown_cancelled_callback'>
<title>The Shutdown Cancelled Callback</title>
<para>
The Shutdown Cancelled callback is of type
<function>SmcShutdownCancelledProc</function>
</para>
<funcsynopsis id='smcshutdowncancelledproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmcShutdownCancelledProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>Client data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends a “Shutdown Cancelled” message
when the user cancelled the shutdown during an interaction
(see <link linkend='interacting_with_the_user'>section 5.5,
“Interacting With the User”</link>). The client can now
continue as if the shutdown had never happened. If the client has not
called <function>SmcSaveYourselfDone</function> yet, it can either
abort the save and then call <function>SmcSaveYourselfDone</function>
with the success argument set to <constant>False</constant> or it can
continue with the save and then call <function>SmcSaveYourselfDone</function>
with the <parameter>success</parameter> argument set to reflect the outcome
of the save.
</para>
</sect2>
</sect1>
<sect1 id='closing_the_connection'><title>Closing the Connection</title>
<para>
To close a connection with a session manager,
use <function>SmcCloseConnection</function>
</para>
<funcsynopsis id='smccloseconnection'>
<funcprototype>
<funcdef>SmcCloseStatus <function>SmcCloseConnection</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>int <parameter>count</parameter></paramdef>
<paramdef>char **<parameter>reason_msgs</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>count</parameter></term>
<listitem><para>The number of reasons for closing the connection.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>reason_msgs</parameter></term>
<listitem><para>The reasons for closing the connection.</para></listitem>
</varlistentry>
</variablelist>
<para>
The <parameter>reason_msgs</parameter> argument will most likely be
<constant>NULL</constant> if resignation is expected by the client.
Otherwise, it contains a list of null-terminated Compound Text strings
representing the reason for termination. The session manager should
display these reason messages to the user.
</para>
<para>
Note that SMlib used the ICE protocol to establish a connection with
the session manager, and various protocols other than session
management may be active on the ICE connection.
When <function>SmcCloseConnection</function> is called, the ICE
connection will be closed only if all protocols have been shutdown on
the connection. Check the ICElib standard
for <function>IceAddConnectionWatch</function>
and <function>IceRemoveConnectionWatch</function> to learn how to set
up a callback to be invoked each time an ICE connection is opened or
closed. Typically this callback adds/removes the ICE file descriptor
from the list of active descriptors to call <function>select</function> on
(or calls <function>XtAppAddInput</function> or
<function>XtRemoveInput</function>).
</para>
<para>
<function>SmcCloseConnection</function> returns one of the following values:
<itemizedlist mark='bullet'>
<listitem><para>
<constant>SmcClosedNow</constant> - the ICE connection was closed at
this time, the watch procedures were invoked, and the connection was freed.
</para></listitem>
<listitem><para>
<constant>SmcClosedASAP</constant> - an IO error had occurred on the
connection, but <function>SmcCloseConnection</function> is being
called within a nested <function>IceProcessMessages</function> The
watch procedures have been invoked at this time, but the connection
will be freed as soon as possible (when the nesting level reaches zero
and <function>IceProcessMessages</function> returns a status
of <function>IceProcessMessagesConnectionClosed</function>
</para> </listitem>
<listitem><para>
<constant>SmcConnectionInUse</constant> - the connection was not closed at
this time, because it is being used by other active protocols.
</para> </listitem>
</itemizedlist>
</para>
</sect1>
<sect1 id='modifying_callbacks'>
<title>Modifying Callbacks</title>
<para>
To modify callbacks set up in <function>SmcOpenConnection</function>
use <function>SmcModifyCallbacks</function>
</para>
<funcsynopsis id='smcmodifycallbacks'>
<funcprototype>
<funcdef>void <function>SmcModifyCallbacks</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>unsigned long <parameter>mask</parameter></paramdef>
<paramdef>SmcCallbacks *<parameter>callbacks</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>mask</parameter></term>
<listitem><para>A mask indicating which callbacks to modify.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>callbacks</parameter></term>
<listitem><para>The new callbacks.</para></listitem>
</varlistentry>
</variablelist>
<para>
When specifying a value for the <parameter>mask</parameter> argument,
the following values may be ORed together:
<simplelist type='vert'>
<member><constant>SmcSaveYourselfProcMask</constant></member>
<member><constant>SmcDieProcMask</constant></member>
<member><constant>SmcSaveCompleteProcMask</constant></member>
<member><constant>SmcShutdownCancelledProcMask</constant></member>
</simplelist>
</para>
</sect1>
<sect1 id='setting_deleting_and_retrieving_session_management_properties'>
<title>Setting, Deleting, and Retrieving Session Management Properties</title>
<para>
To set session management properties for this client,
use <function>SmcSetProperties</function>
</para>
<funcsynopsis id='smcsetproperties'>
<funcprototype>
<funcdef>void <function>SmcSetProperties</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>SmProp **<parameter>props</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>props</parameter></term>
<listitem><para>The list of properties to set.</para></listitem>
</varlistentry>
</variablelist>
<para>
The properties are specified as an array of property pointers.
Previously set property values may be over-written using
the <function>SmcSetProperties</function> function. Note that the
session manager is not expected to restore property values when the
session is restarted. Because of this, clients should not try to use
the session manager as a database for storing application specific state.
</para>
<para>
For a description of session management properties and
the <structname>SmProp</structname> structure,
see <link linkend='session_management_properties'>section 7,
“Session Management Properties.”</link>
</para>
<para>
To delete properties previously set by the client,
use <function>SmcDeleteProperties</function>
</para>
<funcsynopsis id='smcdeleteproperties'>
<funcprototype>
<funcdef>void <function>SmcDeleteProperties</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>char **<parameter>prop_names</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>prop_names</parameter></term>
<listitem><para>The list of properties to set.</para></listitem>
</varlistentry>
</variablelist>
<para>
To get properties previously stored by the client,
use <function>SmcGetProperties</function>
</para>
<funcsynopsis id='smcgetproperties'>
<funcprototype>
<funcdef>Status <function>SmcGetProperties</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmcPropReplyProc <parameter>prop_reply_proc</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>prop_reply_proc</parameter></term>
<listitem><para>The callback to be invoked when the properties reply comes back.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>This pointer to client data will be passed to the <function>SmcPropReplyProc</function> callback.</para></listitem>
</varlistentry>
</variablelist>
<para>
The return value of <function>SmcGetProperties</function> is zero for
failure and a positive value for success.
</para>
<para>
Note that the library does not block until the properties reply comes
back. Rather, a callback of type <function>SmcPropReplyProc</function>
is invoked when the data is ready.
</para>
<funcsynopsis id='smcpropreplyproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmcPropReplyProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>SmProp **<parameter>props</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>This pointer to client data will be passed to the <function>SmcPropReplyProc</function> callback.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties returned.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>props</parameter></term>
<listitem><para>The list of properties returned.</para></listitem>
</varlistentry>
</variablelist>
<para>
To free each property, use <function>SmFreeProperty</function>
(see <link linkend='freeing_data'>section 8, “Freeing
Data”</link>). To free the actual array of pointers,
use <function>free</function>
</para>
</sect1>
<sect1 id='interacting_with_the_user'>
<title>Interacting With the User</title>
<para>
After receiving a “Save Yourself” message with an
<parameter>interact_style</parameter> of
<constant>SmInteractStyleErrors</constant>
or <constant>SmInteractStyleAny</constant> the client may choose to
interact with the user. Because only one client can interact with the
user at a time, the client must call <function>SmcInteractRequest</function>
and wait for an “Interact” message from the session manager.
</para>
<funcsynopsis id='smcinteractrequest'>
<funcprototype>
<funcdef>Status <function>SmcInteractRequest</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>int <parameter>dialog_type</parameter></paramdef>
<paramdef>SmcInteractProc <parameter>interact_proc</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>dialog_type</parameter></term>
<listitem><para>The type of dialog the client wishes to present to the user.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>interact_proc</parameter></term>
<listitem><para>The callback to be invoked when the “Interact” message arrives from the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>
This pointer to client data will be passed to
the <function>SmcInteractProc</function> callback when the
“Interact” message arrives.
</para></listitem>
</varlistentry>
</variablelist>
<para>
The return value of <function>SmcInteractRequest</function> is zero
for failure and a positive value for success.
</para>
<para>
The <parameter>dialog_type</parameter> argument specifies
either <constant>SmDialogError</constant> indicating that the client
wants to start an error dialog, or <constant>SmDialogNormal</constant>
meaning that the client wishes to start a nonerror dialog.
</para>
<para>
Note that if a shutdown is in progress, the user may have the option
of cancelling the shutdown. If the shutdown is cancelled, the clients
that have not interacted yet with the user will receive a
“Shutdown Cancelled” message instead of the
“Interact” message.
</para>
<para>
The <function>SmcInteractProc</function> callback will be invoked when
the “Interact” message arrives from the session manager.
</para>
<funcsynopsis id='smcinteractproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmcInteractProc</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>Client data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
<para>
After interacting with the user (in response to an “Interact”
message), you should call <function>SmcInteractDone</function>
</para>
<funcsynopsis id='smcinteractdone'>
<funcprototype>
<funcdef>void <function>SmcInteractDone</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>Bool <parameter>cancel_shutdown</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>cancel_shutdown</parameter></term>
<listitem><para>If <constant>True</constant>, indicates that the user requests that the entire shutdown be cancelled.</para></listitem>
</varlistentry>
</variablelist>
<para>
The <parameter>cancel_shutdown</parameter> argument may only be
<constant>True</constant> if the corresponding “Save Yourself”
specified <constant>True</constant> for shutdown
and <constant>SmInteractStyleErrors</constant>
or <constant>SmInteractStyleAny</constant> for
the <parameter>interact_style</parameter>.
</para>
</sect1>
<sect1 id='requesting_a_save_yourself'>
<title>Requesting a Save Yourself</title>
<para>
To request a checkpoint from the session manager,
use <function>SmcRequestSaveYourself</function>
</para>
<funcsynopsis id='smcrequestsaveyourself'>
<funcprototype>
<funcdef>void <function>SmcRequestSaveYourself</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>int <parameter>save_type</parameter></paramdef>
<paramdef>Bool <parameter>shutdown</parameter></paramdef>
<paramdef>int <parameter>interact_style</parameter></paramdef>
<paramdef>Bool <parameter>fast</parameter></paramdef>
<paramdef>Bool <parameter>global</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>save_type</parameter></term>
<listitem><para>Specifies the type of information that should be saved.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>shutdown</parameter></term>
<listitem><para>Specifies if a shutdown is taking place.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>interact_style</parameter></term>
<listitem><para>The type of interaction allowed with the user.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>fast</parameter></term>
<listitem><para>If <constant>True</constant> the client should save its state as quickly as possible.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>global</parameter></term>
<listitem><para>Controls who gets the “Save Yourself.”</para></listitem>
</varlistentry>
</variablelist>
<para>
The <parameter>save_type</parameter>, <parameter>shutdown</parameter>,
<parameter>interact_style</parameter>, and <parameter>fast</parameter>
arguments are discussed in more detail in
<link linkend='the_save_yourself_callback'>section 5.1.1,
“The Save Yourself Callback.”</link>
</para>
<para>
If <parameter>global</parameter> is set to <constant>True</constant> then
the resulting “Save Yourself” should be sent to all clients in the
session. For example, a vendor of a Uninterruptible Power Supply
(<acronym>UPS</acronym>) might include a Session Management client
that would monitor the status of the UPS and generate a fast shutdown
if the power is about to be lost.
</para>
<para>
If global is set to <constant>False</constant> then the “Save
Yourself” should only be sent to the client that requested it.
</para>
</sect1>
<sect1 id='requesting_a_save_yourself_phase_2'>
<title>Requesting a Save Yourself Phase 2</title>
<para>
In response to a “Save Yourself”, the client may request to be
informed when all the other clients are quiescent so that it can save their
state. To do so, use <function>SmcRequestSaveYourselfPhase2</function>
</para>
<funcsynopsis id='smcrequestsaveyourselfphase2'>
<funcprototype>
<funcdef>Status <function>SmcRequestSaveYourselfPhase2</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>SmcSaveYourselfPhase2Proc <parameter>save_yourself_phase2_proc</parameter></paramdef>
<paramdef>SmPointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>save_type_phase2_proc</parameter></term>
<listitem><para>The callback to be invoked when the “Save Yourself Phase 2” message arrives from the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>This pointer to client data will be passed to the <function>SmcSaveYourselfPhase2Proc</function> callback when the “Save Yourself Phase 2” message arrives.</para></listitem>
</varlistentry>
</variablelist>
<para>
The return value of <function>SmcRequestSaveYourselfPhase2</function>
is zero for failure and a positive value for success.
</para>
<para>
This request is needed by clients that manage other clients (for
example, window managers, workspace managers, and so on). The manager
must make sure that all of the clients that are being managed are in
an idle state so that their state can be saved.
</para>
</sect1>
<sect1 id='completing_a_save_yourself'>
<title>Completing a Save Yourself</title>
<para>
After saving state in response to a “Save Yourself”
message, you should call <function>SmcSaveYourselfDone</function>
</para>
<funcsynopsis id='smcsaveyourselfdone'>
<funcprototype>
<funcdef>void <function>SmcSaveYourselfDone</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>Bool <parameter>success</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>success</parameter></term>
<listitem><para>If <constant>True</constant> the “Save Yourself” operation was completed successfully.</para></listitem>
</varlistentry>
</variablelist>
<para>
Before calling <function>SmcSaveYourselfDone</function> the client
must have set each required property at least once since the client
registered with the session manager.
</para>
</sect1>
<sect1 id='using_smc_informational_functions'>
<title>Using Smc Informational Functions</title>
<funcsynopsis id='smcprotocolversion'>
<funcprototype>
<funcdef>int <function>SmcProtocolVersion</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcProtocolVersion</function> returns the major version of
the session management protocol associated with this session.
</para>
<funcsynopsis id='smcprotocolrevision'>
<funcprototype>
<funcdef>int <function>SmcProtocolRevision</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcProtocolRevision</function> returns the minor version of
the session management protocol associated with this session.
</para>
<funcsynopsis id='smcvendor'>
<funcprototype>
<funcdef>char *<function>SmcVendor</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcVendor</function> returns a string that provides some
identification of the owner of the session manager. The string should
be freed with a call to <function>free</function>
</para>
<funcsynopsis id='smcrelease'>
<funcprototype>
<funcdef>char *<function>SmcRelease</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcRelease</function> returns a string that provides the
release number of the session manager. The string should be freed
with a call to <function>free</function>
</para>
<funcsynopsis id='smcclientid'>
<funcprototype>
<funcdef>char *<function>SmcClientID</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcClientID</function> returns a null-terminated string for
the client ID associated with this connection. This information was
also returned in <function>SmcOpenConnection</function> (it is
provided here for convenience). Call <function>free</function> on
this pointer when the client ID is no longer needed.
</para>
<funcsynopsis id='smcgeticeconnection'>
<funcprototype>
<funcdef>IceConn <function>SmcGetIceConnection</function></funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmcGetIceConnection</function> returns the ICE connection
object associated with this session management connection object. The
ICE connection object can be used to get some additional information
about the connection. Some of the more useful functions which can be
used on the IceConn are <function>IceConnectionNumber</function>,
<function>IceConnectionString</function>,
<function>IceLastSentSequenceNumber</function>,
<function>IceLastReceivedSequenceNumber</function>,
and <function>IcePing</function>. For further information, see
the <citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</sect1>
<sect1 id='error_handling'>
<title>Error Handling</title>
<para>
If the client receives an unexpected protocol error from the session
manager, an error handler is invoked by SMlib. A default error
handler exists that simply prints the error message
to <varname>stderr</varname> and exits if the severity of the error
is fatal. The client can change this error handler by calling
the <function>SmcSetErrorHandler</function> function.
</para>
<funcsynopsis id='smcseterrorhandler'>
<funcprototype>
<funcdef>SmcErrorHandler <function>SmcSetErrorHandler</function></funcdef>
<paramdef>SmcErrorHandler <parameter>handler</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
The error handler. You should pass <constant>NULL</constant> to
restore the default handler.
</para>
<para>
<function>SmcSetErrorHandler</function> returns the previous error handler.
</para>
<para>
The <function>SmcErrorHandler</function> has the following type:
</para>
<funcsynopsis id='smcerrorhandler'>
<funcprototype>
<funcdef>typedef void (*<function>SmcErrorHandler</function>)</funcdef>
<paramdef>SmcConn <parameter>smc_conn</parameter></paramdef>
<paramdef>Bool <parameter>swap</parameter></paramdef>
<paramdef>int <parameter>offending_minor_opcode</parameter></paramdef>
<paramdef>unsigned long <parameter>offending_sequence_num</parameter></paramdef>
<paramdef>int <parameter>error_class</parameter></paramdef>
<paramdef>int <parameter>severity</parameter></paramdef>
<paramdef>IcePointer <parameter>values</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>smc_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>swap</parameter></term>
<listitem><para>A flag that indicates if the specified values need byte swapping.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>offending_minor_opcode</parameter></term>
<listitem><para>The minor opcode of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>offending_sequence_num</parameter></term>
<listitem><para>The sequence number of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_class</parameter></term>
<listitem><para>The error class of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>severity</parameter></term>
<listitem><para><constant>IceCanContinue</constant>,
<constant>IceFatalToProtocol</constant>, or
<constant>IceFatalToConnection</constant>
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>values</parameter></term>
<listitem><para>Any additional error values specific to the minor opcode and class.</para></listitem>
</varlistentry>
</variablelist>
<para>
Note that this error handler is invoked for protocol related errors.
To install an error handler to be invoked when an IO error occurs, use
<function>IceSetIOErrorHandler</function> For further information, see
the <citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</sect1>
</chapter>
<chapter id='session_management_server'>
<title>Session Management Server (<acronym>Sms</acronym>) Functions</title>
<para>
This section discusses how Session Management servers:
<itemizedlist mark='bullet'>
<listitem><para>Initialize the library</para></listitem>
<listitem><para>Register the client</para></listitem>
<listitem><para>Send a “Save Yourself” message</para></listitem>
<listitem><para>Send a “Save Yourself Phase 2” message</para></listitem>
<listitem><para>Send an “Interact” message</para></listitem>
<listitem><para>Send a “Save Complete” message</para></listitem>
<listitem><para>Send a “Die” message</para></listitem>
<listitem><para>Cancel a shutdown</para></listitem>
<listitem><para>Return properties</para></listitem>
<listitem><para>Ping a client</para></listitem>
<listitem><para>Clean up after a client disconnects</para></listitem>
<listitem><para>Use Sms informational functions</para></listitem>
<listitem><para>Handle errors</para></listitem>
</itemizedlist>
</para>
<sect1 id='initializing_the_library'>
<title>Initializing the Library</title>
<para>
<function>SmsInitialize</function> is the first SMlib function that
should be called by a session manager. It provides information about
the session manager and registers a callback that will be invoked each
time a new client connects to the session manager.
</para>
<funcsynopsis id='smsinitialize'>
<funcprototype>
<funcdef>Status <function>SmsInitialize</function></funcdef>
<paramdef>char *<parameter>vendor</parameter></paramdef>
<paramdef>char *<parameter>release</parameter></paramdef>
<paramdef>SmsNewClientProc <parameter>new_client_proc</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>IceHostBasedAuthProc <parameter>host_based_auth_proc</parameter></paramdef>
<paramdef>int <parameter>error_length</parameter></paramdef>
<paramdef>char *<parameter>error_string_ret</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>vendor</parameter></term>
<listitem><para>A string specifying the session manager vendor.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>release</parameter></term>
<listitem><para>A string specifying the session manager release number.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>new_client_proc</parameter></term>
<listitem><para>Callback to be invoked each time a new client connects to the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>When the <function>SmsNewClientProc</function> callback is invoked, this pointer to manager data will be passed.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>host_based_auth_proc</parameter></term>
<listitem><para>Host based authentication callback.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_length</parameter></term>
<listitem><para>Length of the <parameter>error_string_ret</parameter> argument passed in.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_string_ret</parameter></term>
<listitem><para>
Returns a null-terminated error message, if any.
The <parameter>error_string_ret</parameter> points to user supplied memory.
No more than <parameter>error_length</parameter> bytes are used.
</para></listitem>
</varlistentry>
</variablelist>
<para>
After the <function>SmsInitialize</function> function is called, the
session manager should call the <function>IceListenForConnections</function>
function to listen for new connections. Afterwards, each time a
client connects, the session manager should
call <function>IceAcceptConnection</function>
</para>
<para>
See <link linkend='authentication_of_clients'>section 9,
“Authentication of Clients,”</link> for more details on
authentication (including host based authentication). Also see
the <citetitle pubwork='article'>Inter-Client Exchange
Library</citetitle> standard for further details on listening for and
accepting ICE connections.
</para>
<para>
Each time a new client connects to the session manager,
the <function>SmsNewClientProc</function> callback is invoked. The
session manager obtains a new opaque connection object that it should
use for all future interaction with the client. At this time, the
session manager must also register a set of callbacks to respond to
the different messages that the client might send.
</para>
<funcsynopsis id='smsnewclientproc'>
<funcprototype>
<funcdef>typedef Status (*<function>SmsNewClientProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>unsigned long *<parameter>mask_ret</parameter></paramdef>
<paramdef>SmsCallbacks *<parameter>callbacks_ret</parameter></paramdef>
<paramdef>char **<parameter>failure_reason_ret</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>A new opaque connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>mask_ret</parameter></term>
<listitem><para>On return, indicates which callbacks were set by the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>callbacks_ret</parameter></term>
<listitem><para>On return, contains the callbacks registered by the session manager.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>failure_reason_ret</parameter></term>
<listitem><para>Failure reason returned.</para></listitem>
</varlistentry>
</variablelist>
<para>
If a failure occurs, the <function>SmsNewClientProc</function> should
return a zero status as well as allocate and return a failure reason
string in <parameter>failure_reason_ret</parameter>.
SMlib will be responsible for freeing this memory.
</para>
<para>
The session manager must register a set of callbacks to respond to
client events. The <parameter>mask_ret</parameter> argument specifies
which callbacks are set. All of the callbacks specified in this version of
SMlib are mandatory. The <parameter>mask_ret</parameter> argument is
necessary in order to maintain backwards compatibility in future versions
of the library.
</para>
<para>
The following values may be ORed together to obtain a mask value:
<simplelist type='vert'>
<member><constant>SmsRegisterClientProcMask</constant></member>
<member><constant>SmsInteractRequestProcMask</constant></member>
<member><constant>SmsInteractDoneProcMask</constant></member>
<member><constant>SmsSaveYourselfRequestProcMask</constant></member>
<member><constant>SmsSaveYourselfP2RequestProcMask</constant></member>
<member><constant>SmsSaveYourselfDoneProcMask</constant></member>
<member><constant>SmsCloseConnectionProcMask</constant></member>
<member><constant>SmsSetPropertiesProcMask</constant></member>
<member><constant>SmsDeletePropertiesProcMask</constant></member>
<member><constant>SmsGetPropertiesProcMask</constant></member>
</simplelist>
</para>
<para>
For each callback, the session manager can register a pointer to
manager data specific to that callback. This pointer will be passed
to the callback when it is invoked by SMlib.
</para>
<synopsis>
typedef struct {
struct {
SmsRegisterClientProc callback;
SmPointer manager_data;
} register_client;
struct {
SmsInteractRequestProc callback;
SmPointer manager_data;
} interact_request;
struct {
SmsInteractDoneProc callback;
SmPointer manager_data;
} interact_done;
struct {
SmsSaveYourselfRequestProc callback;
SmPointer manager_data;
} save_yourself_request;
struct {
SmsSaveYourselfPhase2RequestProc callback;
SmPointer manager_data;
} save_yourself_phase2_request;
struct {
SmsSaveYourselfDoneProc callback;
SmPointer manager_data;
} save_yourself_done;
struct {
SmsCloseConnectionProc callback;
SmPointer manager_data;
} close_connection;
struct {
SmsSetPropertiesProc callback;
SmPointer manager_data;
} set_properties;
struct {
SmsDeletePropertiesProc callback;
SmPointer manager_data;
} delete_properties;
struct {
SmsGetPropertiesProc callback;
SmPointer manager_data;
} get_properties;
} SmsCallbacks;
</synopsis>
<sect2 id='the_register_client_callback'>
<title>The Register Client Callback</title>
<para>
The Register Client callback is the first callback that will be
invoked after the client connects to the session manager. Its type
is <function>SmsRegisterClientProc</function>
</para>
<funcsynopsis id='smsregisterclientproc'>
<funcprototype>
<funcdef>typedef Status (*<function>SmsRegisterClientProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>char *<parameter>previous_id</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>previous_id</parameter></term>
<listitem><para>The client ID from the previous session.</para></listitem>
</varlistentry>
</variablelist>
<para>
Before any further interaction takes place with the client, the client
must be registered with the session manager.
</para>
<para>
If the client is being restarted from a previous session,
<parameter>previous_id</parameter> will contain a null-terminated string
representing the client ID from the previous session.
Call <function>free</function> on the <parameter>previous_id</parameter>
pointer when it is no longer needed. If the client is first joining the
session, <parameter>previous_id</parameter> will be <constant>NULL</constant>.
</para>
<para>
If <parameter>previous_id</parameter> is invalid, the session manager should
not register the client at this time. This callback should return a status
of zero, which will cause an error message to be sent to the client. The
client should re-register with previous_id set to <constant>NULL</constant>.
</para>
<para>
Otherwise, the session manager should register the client with a unique
client ID by calling the <function>SmsRegisterClientReply</function>
function (to be discussed shortly), and the
<function>SmsRegisterClientProc</function> callback should return a
status of one.
</para>
</sect2>
<sect2 id='the_interact_request_callback'>
<title>The Interact Request Callback</title>
<para>
The Interact Request callback is of
type <function>SmsInteractRequestProc</function>
</para>
<funcsynopsis id='smsinteractrequestproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsInteractRequestProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>int <parameter>dialog_type</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>dialog_type</parameter></term>
<listitem><para>The type of dialog the client wishes to present to the user.</para></listitem>
</varlistentry>
</variablelist>
<para>
When a client receives a “Save Yourself” message with an
<parameter>interact_style</parameter> of
<constant>SmInteractStyleErrors</constant>
or <constant>SmInteractStyleAny</constant> the client may choose to
interact with the user. Because only one client can interact with the
user at a time, the client must request to interact with the user.
The session manager should keep a queue of all clients wishing to
interact. It should send an “Interact” message to one
client at a time and wait for an “Interact Done” message
before continuing with the next client.
</para>
<para>
The <parameter>dialog_type</parameter> argument specifies
either <constant>SmDialogError</constant> indicating that the client
wants to start an error dialog, or <constant>SmDialogNormal</constant>
meaning that the client wishes to start a nonerror dialog.
</para>
<para>
If a shutdown is in progress, the user may have the option of
cancelling the shutdown. If the shutdown is cancelled (specified in
the “Interact Done” message), the session manager should
send a “Shutdown Cancelled” message to each client that
requested to interact.
</para>
</sect2>
<sect2 id='the_interact_done_callback'>
<title>The Interact Done Callback</title>
<para>
When the client is done interacting with the user,
the <function>SmsInteractDoneProc</function> callback will be invoked.
</para>
<funcsynopsis id='smsinteractdoneproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsInteractDoneProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>Bool <parameter>cancel_shutdown</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>cancel_shutdown</parameter></term>
<listitem><para>Specifies if the user requests that the entire shutdown be cancelled.</para></listitem>
</varlistentry>
</variablelist>
<para>
Note that the shutdown can be cancelled only if the corresponding
“Save Yourself” specified <constant>True</constant> for
shutdown and <constant>SmInteractStyleErrors</constant>
or <constant>SmInteractStyleAny</constant> for the
<parameter>interact_style</parameter>.
</para>
</sect2>
<sect2 id='the_save_yourself_request_callback'>
<title>The Save Yourself Request Callback</title>
<para>
The Save Yourself Request callback is of
type <function>SmsSaveYourselfRequestProc</function>
</para>
<funcsynopsis id='saveyourselfrequestproc'>
<funcprototype>
<funcdef>typedef void (*<function>SaveYourselfRequestProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>int <parameter>save_type</parameter></paramdef>
<paramdef>Bool <parameter>shutdown</parameter></paramdef>
<paramdef>int <parameter>interact_style</parameter></paramdef>
<paramdef>Bool <parameter>fast</parameter></paramdef>
<paramdef>Bool <parameter>global</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>save_type</parameter></term>
<listitem><para>Specifies the type of information that should be saved.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>shutdown</parameter></term>
<listitem><para>Specifies if a shutdown is taking place.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>interact_style</parameter></term>
<listitem><para>The type of interaction allowed with the user.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>fast</parameter></term>
<listitem><para>If <constant>True</constant> the client should save its state as quickly as possible.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>global</parameter></term>
<listitem><para>Controls who gets the “Save Yourself.”</para></listitem>
</varlistentry>
</variablelist>
<para>
The Save Yourself Request prompts the session manager to initiate a
checkpoint or shutdown. For information on the
<parameter>save_type</parameter>, <parameter>shutdown</parameter>,
<parameter>interact_style</parameter>, and <parameter>fast</parameter>
arguments, see <link linkend='sending_a_save_yourself_message'>section 6.3,
“Sending a Save Yourself Message.”</link>
</para>
<para>
If <parameter>global</parameter> is set to <constant>True</constant> then the
resulting “Save Yourself” should be sent to all applications.
If <parameter>global</parameter> is set to <constant>False</constant> then the
“Save Yourself” should only be sent to the client that requested it.
</para>
</sect2>
<sect2 id='the_save_yourself_phase_2_request_callback'>
<title>The Save Yourself Phase 2 Request Callback</title>
<para>
The Save Yourself Phase 2 Request callback is of
type <function>SmsSaveYourselfPhase2RequestProc</function>
</para>
<funcsynopsis id='smssaveyourselfphase2requestproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsSaveYourselfPhase2RequestProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
<para>
This request is sent by clients that manage other clients (for
example, window managers, workspace managers, and so on). Such
managers must make sure that all of the clients that are being managed
are in an idle state so that their state can be saved.
</para>
</sect2>
<sect2 id='the_save_yourself_done_callback'>
<title>The Save Yourself Done Callback</title>
<para>
When the client is done saving its state in response to a
“Save Yourself” message,
the <function>SmsSaveYourselfDoneProc</function> will be invoked.
</para>
<funcsynopsis id='saveyourselfdoneproc'>
<funcprototype>
<funcdef>typedef void (*<function>SaveYourselfDoneProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>Bool <parameter>success</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>success</parameter></term>
<listitem><para>If <constant>True</constant> the Save Yourself operation was completed successfully.</para></listitem>
</varlistentry>
</variablelist>
<para>
Before the “Save Yourself Done” was sent, the client must
have set each required property at least once since it registered with
the session manager.
</para>
</sect2>
<sect2 id='the_connection_closed_callback'>
<title>The Connection Closed Callback</title>
<para>
If the client properly terminates (that is, it
calls <function>SmcCloseConnection</function>,
the <function>SmsCloseConnectionProc</function> callback is invoked.
</para>
<funcsynopsis id='smscloseconnectionproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsCloseConnectionProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>int <parameter>count</parameter></paramdef>
<paramdef>char **<parameter>reason_msgs</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>count</parameter></term>
<listitem><para>The number of reason messages.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>reason_msgs</parameter></term>
<listitem><para>The reasons for closing the connection.</para></listitem>
</varlistentry>
</variablelist>
<para>
The <parameter>reason_msgs</parameter> argument will most likely
be <constant>NULL</constant> and the <parameter>count</parameter>
argument zero (0) if resignation is expected by the user. Otherwise,
it contains a list of null-terminated Compound Text strings
representing the reason for termination. The session manager should
display these reason messages to the user.
</para>
<para>
Call <function>SmFreeReasons</function> to free the reason messages.
For further information, see
<link linkend='freeing_data'>section 8, “Freeing Data”</link>
</para>
</sect2>
<sect2 id='the_set_properties_callback'>
<title>The Set Properties Callback</title>
<para>
When the client sets session management properties,
the <function>SmsSetPropertiesProc</function> callback will be invoked.
</para>
<funcsynopsis id='smssetpropertiesproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsSetPropertiesProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>SmProp **<parameter>props</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>props</parameter></term>
<listitem><para>The list of properties to set.</para></listitem>
</varlistentry>
</variablelist>
<para>
The properties are specified as an array of property pointers. For a
description of session management properties and
the <structname>SmProp</structname> structure,
see <link linkend='session_management_properties'>section 7,
“Session Management Properties.”</link>
</para>
<para>
Previously set property values may be over-written. Some properties
have predefined semantics. The session manager is required to store
nonpredefined properties.
</para>
<para>
To free each property, use <function>SmFreeProperty</function>.
For further information, see <link linkend='freeing_data'>section 8,
“Freeing Data”</link> You should free the actual array of
pointers with a call to <function>free</function>
</para>
</sect2>
<sect2 id='the_delete_properties_callback'>
<title>The Delete Properties Callback</title>
<para>
When the client deletes session management properties,
the <function>SmsDeletePropertiesProc</function> callback will be invoked.
</para>
<funcsynopsis id='smsdeletepropertiesproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsDeletePropertiesProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>char **<parameter>prop_names</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>prop_names</parameter></term>
<listitem><para>The list of properties to delete.</para></listitem>
</varlistentry>
</variablelist>
<para>
The properties are specified as an array of strings. For a
description of session management properties and
the <structname>SmProp</structname> structure,
see <link linkend='session_management_properties'>section 7,
“Session Management Properties.”</link>
</para>
</sect2>
<sect2 id='the_get_properties_callback'>
<title>The Get Properties Callback</title>
<para>
The <function>SmsGetPropertiesProc</function> callback is invoked when
the client wants to retrieve properties it set.
</para>
<funcsynopsis id='smsgetpropertiesproc'>
<funcprototype>
<funcdef>typedef void (*<function>SmsGetPropertiesProc</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>SmPointer <parameter>manager_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>manager_data</parameter></term>
<listitem><para>Manager data specified when the callback was registered.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager should respond by
calling <function>SmsReturnProperties</function>.
All of the properties set for this client should be returned.
</para>
</sect2>
</sect1>
<sect1 id='registering_the_client'>
<title>Registering the Client</title>
<para>
To register a client (in response to
a <function>SmsRegisterClientProc</function> callback),
use <function>SmsRegisterClientReply</function>.
</para>
<funcsynopsis id='smsregisterclientreply'>
<funcprototype>
<funcdef>Status <function>SmsRegisterClientReply</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>char *<parameter>client_id</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_id</parameter></term>
<listitem><para>A null-terminated string representing a unique client ID.</para></listitem>
</varlistentry>
</variablelist>
<para>
The return value of <function>SmsRegisterClientReply</function> is
zero for failure and a positive value for success. Failure will occur
if SMlib can not allocate memory to hold a copy of the client ID for
it's own internal needs.
</para>
<para>
If a non-<constant>NULL</constant> <parameter>previous_id</parameter> was
specified when the client registered itself, <parameter>client_id</parameter>
should be identical to <parameter>previous_id</parameter>.
</para>
<para>
Otherwise, <parameter>client_id</parameter> should be a unique ID freshly
generated by the session manager. In addition, the session manager should
send a “Save Yourself” message with
<parameter>type</parameter> = <constant>Local</constant>,
<parameter>shutdown</parameter> = <constant>False</constant>,
<parameter>interact-style</parameter> = <constant>None</constant>,
and <parameter>fast</parameter> = <constant>False</constant>
immediately after registering the client.
</para>
<para>
Note that once a client ID has been assigned to the client, the client
keeps this ID indefinitely. If the client is terminated and
restarted, it will be reassigned the same ID. It is desirable to be
able to pass client IDs around from machine to machine, from user to
user, and from session manager to session manager, while retaining the
identity of the client. This, combined with the indefinite
persistence of client IDs, means that client IDs need to be globally
unique.
</para>
<para>
You should call the <function>SmsGenerateClientID</function> function
to generate a globally unique client ID.
</para>
<funcsynopsis id='smsgenerateclientid'>
<funcprototype>
<funcdef>char *<function>SmsGenerateClientID</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
<constant>NULL</constant> will be returned if the ID could not be generated.
Otherwise, the return value of the function is the client ID.
It should be freed with a call to <function>free</function> when
no longer needed.
</para>
</sect1>
<sect1 id='sending_a_save_yourself_message'>
<title>Sending a Save Yourself Message</title>
<para>
To send a “Save Yourself” to a client,
use <function>SmsSaveYourself</function>.
</para>
<funcsynopsis id='smssaveyourself'>
<funcprototype>
<funcdef>void <function>SmsSaveYourself</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>int <parameter>save_type</parameter></paramdef>
<paramdef>Bool <parameter>shutdown</parameter></paramdef>
<paramdef>int <parameter>interact_style</parameter></paramdef>
<paramdef>Bool <parameter>fast</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>save_type</parameter></term>
<listitem><para>Specifies the type of information that should be saved.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>shutdown</parameter></term>
<listitem><para>Specifies if a shutdown is taking place.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>interact_style</parameter></term>
<listitem><para>The type of interaction allowed with the user.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>fast</parameter></term>
<listitem><para>If <constant>True</constant> the client should save its state as quickly as possible.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends a “Save Yourself” message to a
client either to checkpoint it or just before termination so that it
can save its state. The client responds with zero or more “Set
Properties” messages to update the properties indicating how to
restart the client. When all the properties have been set, the client
sends a “Save Yourself Done” message.
</para>
<para>
If <parameter>interact_style</parameter>
is <constant>SmInteractStyleNone</constant> the
client must not interact with the user while saving state.
If <parameter>interact_style</parameter>
is <constant>SmInteractStyleErrors</constant> the
client may interact with the user only if an error condition arises.
If <parameter>interact_style</parameter>
is <constant>SmInteractStyleAny</constant> then the
client may interact with the user for any purpose. The client must
send an “Interact Request” message and wait for an
“Interact” message from the session manager before it can
interact with the user. When the client is done interacting with the
user, it should send an “Interact Done” message. The
“Interact Request” message can be sent any time after a
“Save Yourself” and before a “Save Yourself
Done.”
</para>
<para>
If <parameter>save_type</parameter> is <constant>SmSaveLocal</constant>
the client must update the properties to reflect its current state.
Specifically, it should save enough information to restore the state as
seen by the user of this client. It should not affect the state as seen
by other users.
If <parameter>save_type</parameter> is <constant>SmSaveGlobal</constant>
the user wants the client to commit all of its data to permanent, globally
accessible storage.
If <parameter>save_type</parameter> is <constant>SmSaveBoth</constant>
the client should do both of these (it should first commit the data to
permanent storage before updating its properties).
</para>
<para>
The <parameter>shutdown</parameter> argument specifies whether the session
is being shut down. The interaction is different depending on whether or not
shutdown is set. If not shutting down, then the client can save and
resume normal operation. If shutting down, the client must save and
then must prevent interaction until it receives either a
“Die” or a “Shutdown Cancelled,” because
anything the user does after the save will be lost.
</para>
<para>
The <parameter>fast</parameter> argument specifies that the client should
save its state as quickly as possible. For example, if the session manager
knows that power is about to fail, it should set <parameter>fast</parameter>
to <constant>True</constant>.
</para>
</sect1>
<sect1 id='sending_a_save_yourself_phase_2_message'>
<title>Sending a Save Yourself Phase 2 Message</title>
<para>
In order to send a “Save Yourself Phase 2” message to a
client, use <function>SmsSaveYourselfPhase2</function>
</para>
<funcsynopsis id='smssaveyourselfphase2'>
<funcprototype>
<funcdef>void <function>SmsSaveYourselfPhase2</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends this message to a client that has previously
sent a “Save Yourself Phase 2 Request” message. This
message informs the client that all other clients are in a fixed state
and this client can save state that is associated with other clients.
</para>
</sect1>
<sect1 id='sending_an_interact_message'>
<title>Sending an Interact Message</title>
<para>
To send an “Interact” message to a client,
use <function>SmsInteract</function>.
</para>
<funcsynopsis id='smsinteract'>
<funcprototype>
<funcdef>void <function>SmsInteract</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
The “Interact” message grants the client the privilege of
interacting with the user. When the client is done interacting with
the user, it must send an “Interact Done” message to the
session manager.
</para>
</sect1>
<sect1 id='sending_a_save_complete_message'>
<title>Sending a Save Complete Message</title>
<para>
To send a “Save Complete” message to a client,
use <function>SmsSaveComplete</function>.
</para>
<funcsynopsis id='smssavecomplete'>
<funcprototype>
<funcdef>void <function>SmsSaveComplete</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
The session manager sends this message when it is done with a
checkpoint. The client is then free to change its state.
</para>
</sect1>
<sect1 id='sending_a_die_message'>
<title>Sending a Die Message</title>
<para>
To send a “Die” message to a client,
use <function>SmsDie</function>.
</para>
<funcsynopsis id='smsdie'>
<funcprototype>
<funcdef>void <function>SmsDie</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
Before the session manager terminates, it should wait for a
“Connection Closed” message from each client that it sent
a “Die” message to, timing out appropriately.
</para>
</sect1>
<sect1 id='cancelling_a_shutdown'>
<title>Cancelling a Shutdown</title>
<para>
To cancel a shutdown, use <function>SmsShutdownCancelled</function>.
</para>
<funcsynopsis id='smsshutdowncancelled'>
<funcprototype>
<funcdef>void <function>SmsShutdownCancelled</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
<para>
The client can now continue as if the shutdown had never happened. If
the client has not sent a “Save Yourself Done” message
yet, it can either abort the save and send a “Save Yourself
Done” with the success argument set to <constant>False</constant>
or it can continue with the save and send a “Save Yourself Done”
with the <parameter>success</parameter> argument set to reflect the outcome
of the save.
</para>
</sect1>
<!-- aaaaaaaaaaaaaaaaa -->
<sect1 id='returning_properties'>
<title>Returning Properties</title>
<para>
In response to a “Get Properties” message, the session
manager should call <function>SmsReturnProperties</function>.
</para>
<funcsynopsis id='smsreturnproperties'>
<funcprototype>
<funcdef>void <function>SmsReturnProperties</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>int <parameter>num_props</parameter></paramdef>
<paramdef>SmProp **<parameter>props</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>num_props</parameter></term>
<listitem><para>The number of properties.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>props</parameter></term>
<listitem><para>The list of properties to return to the client.</para></listitem>
</varlistentry>
</variablelist>
<para>
The properties are returned as an array of property pointers. For a
description of session management properties and
the <structname>SmProp</structname> structure,
see <link linkend='session_management_properties'>section 7,
“Session Management Properties.”</link>
</para>
</sect1>
<sect1 id='pinging_a_client'>
<title>Pinging a Client</title>
<para>
To check that a client is still alive, you should use
the <function>IcePing</function> function provided by the ICE library.
To do so, the ICE connection must be obtained using
the <function>SmsGetIceConnection</function>
(see <link linkend='using_sms_informational_functions'>section 6.12,
“Using Sms Informational Functions”</link>).
</para>
<funcsynopsis id='iceping'>
<funcprototype>
<funcdef>void <function>IcePing</function></funcdef>
<paramdef>IceConn <parameter>ice_conn</parameter></paramdef>
<paramdef>IcePingReplyProc <parameter>ping_reply_proc</parameter></paramdef>
<paramdef>IcePointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>ice_conn</parameter></term>
<listitem><para>A valid ICE connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>ping_reply_proc</parameter></term>
<listitem><para>The callback to invoke when the Ping reply arrives.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>This pointer will be passed to the <function>IcePingReplyProc</function> callback.</para></listitem>
</varlistentry>
</variablelist>
<para>
When the Ping reply is ready (if ever),
the <function>IcePingReplyProc</function> callback will be invoked. A
session manager should have some sort of timeout period, after which
it assumes the client has unexpectedly died.
</para>
<funcsynopsis id='icepingreplyproc'>
<funcprototype>
<funcdef>typedef void (*<function>IcePingReplyProc</function>)</funcdef>
<paramdef>IceConn <parameter>ice_conn</parameter></paramdef>
<paramdef>IcePointer <parameter>client_data</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>ice_conn</parameter></term>
<listitem><para>A valid ICE connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>client_data</parameter></term>
<listitem><para>The client data specified in the call to <function>IcePing</function></para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id='cleaning_up_after_a_client_disconnects'>
<title>Cleaning Up After a Client Disconnects</title>
<para>
When the session manager receives a “Connection Closed”
message or otherwise detects that the client aborted the connection,
it should call the <function>SmsCleanUp</function> function in order
to free up the connection object.
</para>
<funcsynopsis id='smscleanup'>
<funcprototype>
<funcdef>void <function>SmsCleanUp</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id='using_sms_informational_functions'>
<title>Using Sms Informational Functions</title>
<funcsynopsis id='smsprotocolversion'>
<funcprototype>
<funcdef>int <function>SmsProtocolVersion</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmsProtocolVersion</function> returns the major version of
the session management protocol associated with this session.
</para>
<funcsynopsis id='smsprotocolrevision'>
<funcprototype>
<funcdef>int <function>SmsProtocolRevision</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmsProtocolRevision</function> returns the minor version of
the session management protocol associated with this session.
</para>
<funcsynopsis id='smsclientid'>
<funcprototype>
<funcdef>char *<function>SmsClientID</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmsClientID</function> returns a null-terminated string for
the client ID associated with this connection. You should
call <function>free</function> on this pointer when the client ID is
no longer needed.
</para>
<para>
To obtain the host name of a client,
use <function>SmsClientHostName</function>.
This host name will be needed to restart the client.
</para>
<funcsynopsis id='smsclienthostname'>
<funcprototype>
<funcdef>char *<function>SmsClientHostName</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
The string returned is of the form
<parameter>protocol</parameter><literal>/</literal><parameter>hostname</parameter>,
where <parameter>protocol</parameter> is one of
{<literal>tcp</literal>, <literal>decnet</literal>, <literal>local</literal>}.
You should call <function>free</function> on the string returned when
it is no longer needed.
</para>
<funcsynopsis id='smsgeticeconnection'>
<funcprototype>
<funcdef>IceConn <function>SmsGetIceConnection</function></funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
<function>SmsGetIceConnection</function> returns the ICE connection
object associated with this session management connection object. The
ICE connection object can be used to get some additional information
about the connection. Some of the more useful functions which can be
used on the IceConn are <function>IceConnectionNumber</function>
and <function>IceLastSequenceNumber</function>.
For further information, see the
<citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</sect1>
<sect1 id='error_handling2'>
<title>Error Handling</title>
<para>
If the session manager receives an unexpected protocol error from a
client, an error handler is invoked by SMlib. A default error handler
exists which simply prints the error message (it does not exit). The
session manager can change this error handler by
calling <function>SmsSetErrorHandler</function>.
</para>
<funcsynopsis id='smsseterrorhandler'>
<funcprototype>
<funcdef>SmsErrorHandler <function>SmsSetErrorHandler</function></funcdef>
<paramdef>SmsErrorHandler <parameter>handler</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<para>
The error handler. You should pass <constant>NULL</constant>
to restore the default handler.
</para>
<para>
<function>SmsSetErrorHandler</function> returns the previous error handler.
The <function>SmsErrorHandler</function> has the following type:
</para>
<funcsynopsis id='smserrorhandler'>
<funcprototype>
<funcdef>typedef void (*<function>SmsErrorHandler</function>)</funcdef>
<paramdef>SmsConn <parameter>sms_conn</parameter></paramdef>
<paramdef>Bool <parameter>swap</parameter></paramdef>
<paramdef>int <parameter>offending_minor_opcode</parameter></paramdef>
<paramdef>unsigned long <parameter>offending_sequence_num</parameter></paramdef>
<paramdef>int <parameter>error_class</parameter></paramdef>
<paramdef>int <parameter>severity</parameter></paramdef>
<paramdef>IcePointer <parameter>values</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>sms_conn</parameter></term>
<listitem><para>The session management connection object.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>swap</parameter></term>
<listitem><para>A flag which indicates if the specified values need byte swapping.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>offending_minor_opcode</parameter></term>
<listitem><para>The minor opcode of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>offending_sequence_num</parameter></term>
<listitem><para>The sequence number of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>error_class</parameter></term>
<listitem><para>The error class of the offending message.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>severity</parameter></term>
<listitem><para>
<constant>IceCanContinue</constant>,
<constant>IceFatalToProtocol</constant>, or
<constant>IceFatalToConnection</constant>
</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>values</parameter></term>
<listitem><para>Any additional error values specific to the minor opcode and class.</para></listitem>
</varlistentry>
</variablelist>
<para>
Note that this error handler is invoked for protocol related errors.
To install an error handler to be invoked when an IO error occurs,
use <function>IceSetIOErrorHandler</function>.
For further information, see the
<citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</sect1>
</chapter>
<chapter id='session_management_properties'>
<title>Session Management Properties</title>
<para>
Each property is defined by the <structname>SmProp</structname> structure:
<synopsis>
typedef struct {
char *name; /* name of property */
char *type; /* type of property */
int num_vals; /* number of values */
SmPropValue *vals; /* the list of values */
} SmProp;
typedef struct {
int length; /* the length of the value */
SmPointer value; /* the value */
} SmPropValue;
</synopsis>
</para>
<para>
The X Session Management Protocol defines a list of predefined
properties, several of which are required to be set by the client.
The following table specifies the predefined properties and indicates
which ones are required. Each property has a type associated with it.
</para>
<para>
A type of <type>SmCARD8</type> indicates that there is a single 1-byte value.
A type of <type>SmARRAY8</type> indicates that there is a single array of bytes.
A type of <type>SmLISTofARRAY8</type> indicates that there is a list of array of
bytes.
</para>
<informaltable pgwide='0' frame='none'>
<tgroup cols='4' align='center'>
<colspec colname='c1'/>
<colspec colname='c2'/>
<colspec colname='c3'/>
<colspec colname='c4'/>
<thead>
<row>
<entry align='left'>Name</entry>
<entry align='left'>Type</entry>
<entry align='left'><acronym>POSIX</acronym> Type</entry>
<entry align='center'>Required</entry>
</row>
</thead>
<tbody>
<row>
<entry align='left'><property>SmCloneCommand</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>Yes</entry>
</row>
<row>
<entry align='left'><property>SmCurrentDirectory</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmARRAY8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmDiscardCommand</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>No*</entry>
</row>
<row>
<entry align='left'><property>SmEnvironment</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmProcessID</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmARRAY8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmProgram</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmARRAY8</type></entry>
<entry align='center'>Yes</entry>
</row>
<row>
<entry align='left'><property>SmRestartCommand</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>Yes</entry>
</row>
<row>
<entry align='left'><property>SmResignCommand</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmRestartStyleHint</property></entry>
<entry align='left'><type>SmCARD8</type></entry>
<entry align='left'><type>SmCARD8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmShutdownCommand</property></entry>
<entry align='left'>OS-specific</entry>
<entry align='left'><type>SmLISTofARRAY8</type></entry>
<entry align='center'>No</entry>
</row>
<row>
<entry align='left'><property>SmUserID</property></entry>
<entry align='left'><type>SmARRAY8</type></entry>
<entry align='left'><type>SmARRAY8</type></entry>
<entry align='center'>Yes</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>
* Required if any state is stored in an external repository (for
example, state file).
</para>
<itemizedlist mark='bullet'>
<listitem><para><property>SmCloneCommand</property></para>
<para>
This is like the <property>SmRestartCommand</property>, except it restarts a
copy of the application. The only difference is that the application does not
supply its client ID at register time. On <acronym>POSIX</acronym> systems,
this should be of type <type>SmLISTofARRAY8</type>.
</para></listitem>
<listitem><para><property>SmCurrentDirectory</property></para>
<para>
On <acronym>POSIX</acronym>-based systems, this specifies the value of the
current directory that needs to be set up prior to starting the
<property>SmProgram</property> and should of type <type>SmARRAY8</type>.
</para></listitem>
<listitem><para><property>SmDiscardCommand</property></para>
<para>
The discard command contains a command that when delivered to the host
that the client is running on (determined from the connection), will
cause it to discard any information about the current state. If this
command is not specified, the Session Manager will assume that all of
the client's state is encoded in the <property>SmRestartCommand</property>.
On <acronym>POSIX</acronym> systems, the type should be
<type>SmLISTofARRAY8</type>.
</para></listitem>
<listitem><para><property>SmEnvironment</property></para>
<para>
On <acronym>POSIX</acronym> based systems, this will be of type
<type>SmLISTofARRAY8</type>, where the <type>ARRAY8</type>s alternate between
environment variable name and environment variable value.
</para></listitem>
<listitem><para><property>SmProcessID</property></para>
<para>
This specifies an OS-specific identifier for the process.
On <acronym>POSIX</acronym> systems, this should contain the return value
of <function>getpid</function> turned into a Latin-1 (decimal) string.
</para></listitem>
<listitem><para><property>SmProgram</property></para>
<para>
This is the name of the program that is running. On <acronym>POSIX</acronym>
systems, this should be first parameter passed to <function>execve</function>
and should be of type <type>SmARRAY8</type>.
</para></listitem>
<listitem><para><property>SmRestartCommand</property></para>
<para>
The restart command contains a command that, when delivered to the
host that the client is running on (determined from the connection),
will cause the client to restart in its current state.
On <acronym>POSIX</acronym>-based systems, this is of
type <type>SmLISTofARRAY8</type>, and each of the elements in
the array represents an element in the <varname>argv</varname>
array. This restart command should ensure that the client restarts
with the specified client-ID.
</para></listitem>
<listitem><para><property>SmResignCommand</property></para>
<para>
A client that sets the <property>SmRestartStyleHint</property>
to <constant>SmRestartAnyway</constant> uses this property to specify a
command that undoes the effect of the client and removes any saved state.
As an example, consider a user that runs <command>xmodmap</command> which
registers with the Session Manager,
sets <property>SmRestartStyleHint</property>
to <constant>SmRestartAnyway</constant>, and then
terminates. To allow the Session Manager (at the user's request) to
undo this, <command>xmodmap</command> would register a
<property>SmResignCommand</property> that undoes the effects of
the <command>xmodmap</command>.
</para></listitem>
<listitem><para><property>SmRestartStyleHint</property></para>
<para>
If the <property>SmRestartStyleHint</property> is present, it will contain the
style of restarting the client prefers. If this style is not specified,
<constant>SmRestartIfRunning</constant> is assumed.
The possible values are as follows:
<informaltable pgwide='0' frame='none'>
<tgroup cols='2' align='center'>
<colspec colname='c1'/>
<colspec colname='c2'/>
<thead>
<row>
<entry align='left'>Name</entry>
<entry align='right'>Value</entry>
</row>
</thead>
<tbody>
<row>
<entry align='left'><constant>SmRestartIfRunning</constant></entry>
<entry align='right'>0</entry>
</row>
<row>
<entry align='left'><constant>SmRestartAnyway</constant></entry>
<entry align='right'>1</entry>
</row>
<row>
<entry align='left'><constant>SmRestartImmediately</constant></entry>
<entry align='right'>2</entry>
</row>
<row>
<entry align='left'><constant>SmRestartNever</constant></entry>
<entry align='right'>3</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</para>
<para>
The <constant>SmRestartIfRunning</constant> style is used in the usual case.
The client should be restarted in the next session if it was running at
the end of the current session.
</para>
<para>
The <constant>SmRestartAnyway</constant> style is used to tell the Session
Manager that the application should be restarted in the next session even if
it exits before the current session is terminated. It should be noted that
this is only a hint and the Session Manager will follow the policies
specified by its users in determining what applications to restart.
</para>
<para>
A client that uses <constant>SmRestartAnyway</constant> should also set the
<property>SmResignCommand</property> and <property>SmShutdownCommand</property>
properties to commands that undo the state of the client after it exits.
</para>
<para>
The SmRestartImmediately style is like SmRestartAnyway, but, in addition, the client is meant to run continuously. If the client exits, the Session Manager should try to restart it in the current session.
</para>
<para>
<constant>SmRestartNever</constant> style specifies that the client does not
wish to be restarted in the next session.
</para>
</listitem>
<listitem><para><property>SmShutdownCommand</property></para>
<para>
This command is executed at shutdown time to clean up after a client
that is no longer running but retained its state by setting
<property>SmRestartStyleHint</property> to
<constant>SmRestartAnyway</constant>. The client must not remove any saved
state as the client is still part of the session. As an
example, consider a client that turns on a camera at start up time.
This client then exits. At session shutdown, the user wants the
camera turned off. This client would set the
<property>SmRestartStyleHint</property> to
<constant>SmRestartAnyway</constant> and would register
a <property>SmShutdownCommand</property> that would turn off the camera.
</para></listitem>
<listitem><para><property>SmUserID</property></para>
<para>
Specifies the user ID. On <acronym>POSIX</acronym>-based systems, this will
contain the user's name (the <structfield>pw_name</structfield> member of
<structname>struct passwd</structname>).
</para></listitem>
</itemizedlist>
</chapter>
<chapter id='freeing_data'>
<title>Freeing Data</title>
<para>
To free an individual property, use <function>SmFreeProperty</function>
</para>
<funcsynopsis id='smfreeproperty'>
<funcprototype>
<funcdef>void <function>SmFreeProperty</function></funcdef>
<paramdef>SmProp *<parameter>prop</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>prop</parameter></term>
<listitem><para>The property to free.</para></listitem>
</varlistentry>
</variablelist>
<para>
To free the reason strings from
the <function>SmsCloseConnectionProc</function> callback,
use <function>SmFreeReasons</function>
</para>
<funcsynopsis id='smfreereasons'>
<funcprototype>
<funcdef>void <function>SmFreeReasons</function></funcdef>
<paramdef>int <parameter>count</parameter></paramdef>
<paramdef>char **<parameter>reasons</parameter></paramdef>
</funcprototype>
</funcsynopsis>
<variablelist remap='IP'>
<varlistentry>
<term><parameter>count</parameter></term>
<listitem><para>The number of reason strings.</para></listitem>
</varlistentry>
<varlistentry>
<term><parameter>reasons</parameter></term>
<listitem><para>The list of reason strings to free.</para></listitem>
</varlistentry>
</variablelist>
</chapter>
<chapter id='authentication_of_clients'>
<title>Authentication of Clients</title>
<para>
As stated earlier, the session management protocol is layered on top
of ICE. Authentication occurs at two levels in the ICE protocol:
<itemizedlist mark='bullet'>
<listitem><para>The first is when an ICE connection is opened.</para></listitem>
<listitem><para>The second is when a Protocol Setup occurs on an ICE connection.</para></listitem>
</itemizedlist>
</para>
<para>
The authentication methods that are available are
implementation-dependent (that is., dependent on the ICElib and SMlib
implementations in use). For further information, see the
<citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</chapter>
<chapter id='working_in_a_multithreaded_environment'>
<title>Working in a Multi-Threaded Environment</title>
<para>
To declare that multiple threads in an application will be using SMlib
(or any other library layered on top of ICElib), you should
call <function>IceInitThreads</function>.
For further information, see the
<citetitle pubwork='article'>Inter-Client Exchange Library</citetitle>
standard.
</para>
</chapter>
<chapter id='acknowledgements'>
<title>Acknowledgements</title>
<para>
Thanks to the following people for their participation in the
X Session Management design: Jordan Brown, Ellis Cohen, Donna Converse,
Stephen Gildea, Vania Joloboff, Stuart Marks, Bob Scheifler, Ralph Swick,
and Mike Wexler.
</para>
</chapter>
</book>
|