<!-- /etc/Pt-web.xml

 Copyright: ©2012–2013, Güralp Systems Ltd.
 Author: Laurence Withers <lwithers@guralp.com>
 License: GPLv3

-->

<server>
	<application-settings location='*'>

		<session-management>
			<!-- If the initial page load takes longer than this, we
			get stuck in a loop continually reloading the page. Wt's
			default is 10s (with a 1s margin of error). -->
			<bootstrap-timeout>60</bootstrap-timeout>

			<!-- We want to avoid multithreaded operation to the
			extent possible. Most of our library code is single
			threaded, and we only have a single CPU. -->
			<dedicated-process>
				<!-- Quite low, but we're an embedded system -->
				<max-num-sessions>20</max-num-sessions>
			</dedicated-process>

			<!-- This fairly short timeout gives us a balance between
			working successfully on slow links yet limiting the max
			number of sessions (as we spawn one session per page at
			the present time; this will change once the menu system is
			converted over). -->
			<timeout>120</timeout>
		</session-management>

		<connector-fcgi>
			<!-- We need 2 child threads. One does the main
			processing; one is used when we cal processEvents() -->
			<num-threads>2</num-threads>
		</connector-fcgi>

		<run-directory>/var/run/Pt-web</run-directory>
		<properties>
			<property name='resourcesURL'>/static</property>
		</properties>

	</application-settings>
</server>
