<?xml version="1.0"?>
<config>
  <AdvancedOptions>
    <AdvancedOption>
      <DisplayName>Command</DisplayName>
      <MaxOccurs>1</MaxOccurs>
      <Name>command</Name>
      <Type>char</Type>
      <Value>gpesyncd --remote</Value>
    </AdvancedOption>
    <AdvancedOption>
      <DisplayName>Debug</DisplayName>
      <MaxOccurs>1</MaxOccurs>
      <Name>debug</Name>
      <Type>ulong</Type>
      <Value>0</Value>
    </AdvancedOption>
  </AdvancedOptions>
  <!-- There are three ways to connect to the GPE device:
	
	1) You can use gpesyncd locally (if opensync is running
	on the same system) by not specifying a <Connection> tag
	at all.

	In this case you can also specify the "command" advanced option 
	to change the shell command which is invoked.  However, specifying 
	the command is not recommended: the default command is:
	gpesyncd - -remote (note the two hyphens should be adjacent but cannot
	be placed together in an XML comment).

	2) You can use SSH to connect to the device by specifying
	<Protocol>ssh</Protocol> within the <Connection><Network> tag.

	In this case, the <Address> tag can also be used.  Note that the 
	<Address> can be a name or an address and may be associated with 
	a particular identify file in the ~/.ssh/config file to allow 
	automatic login.

	You can specify the user to use for the ssh login by specifying the
	<Authentication><Username> tag.  Note that for the Nokia Internet 
	Tablet, the username should be specified as "user".

	In this case you can also specify the "command" advanced option 
	to change the shell command which is invoked.  However, specifying 
	the command is not recommended: the default command is:
	gpesyncd - -remote (note the two hyphens should be adjacent but cannot
	be placed together in an XML comment).

	3) You can connect to a running gpesyncd daemon by specifying the
	<Protocol>gpesyncd</Protocol> within the <Connection><Network> tag.

	In this case, the <Address> and <Port> tags can also be used.

  Either customise the ssh configuration shown below or remove it and uncomment
  one of the other sections.  Each section is configured to show the default values
  used if the tags are not specified. 
  -->
  <Authentication><Username>gpeuser</Username></Authentication>
  <Connection><ActiveConnection>Network</ActiveConnection>
   <Network>
    <Address>127.0.0.1</Address>
    <Protocol>ssh</Protocol>
   </Network>
  </Connection>
  <!-- for local access, specify nothing
  -->
  <!-- for remote gpesyncd access:
  <Connection><ActiveConnection>Network</ActiveConnection>
   <Network>
    <Address>127.0.0.1</Address>
    <Port>6446</Port>
    <Protocol>gpesyncd</Protocol>
   </Network>
  </Connection>
  -->

  <!--
  The <Path> tag within the <Resource> tag with name "vevent20" 
  can be used to specify which GPE calendar should be used for 
  this synchronisation.  If the tag is specified then only the
  named calendar is considered (only events in that calendar will
  be sent from GPE and all events sent to GPE will be stored in
  that calendar).  If the tag is not specified, then all events,
  from all calendars, will be sent from GPE and new events will
  be created in the default calendar.

  Note that an error occurs if the named calendar does not exist.
  Also note that calendar names are case-sensitive.
  -->
  <Resources>
    <Resource>
      <Enabled>1</Enabled>
      <Name>vevent20</Name>
      <ObjType>event</ObjType>
      <!-- <Path>Some Calendar</Path> -->
    </Resource>
    <Resource>
      <Enabled>1</Enabled>
      <Name>vcard30</Name>
      <ObjType>contact</ObjType>
    </Resource>
    <Resource>
      <Enabled>1</Enabled>
      <Name>vtodo20</Name>
      <ObjType>todo</ObjType>
    </Resource>
  </Resources>
</config>
