From 836dd6398f05c1332b3017793ced0a2692bfcd9e Mon Sep 17 00:00:00 2001
From: Andrew McMillan <debian@mcmillan.net.nz>
Date: Wed, 25 Oct 2006 22:44:35 +1300
Subject: [PATCH] More tweaks to public website.

---
 docs/website/clients.php | 21 +++++++++++++++++++++
 docs/website/style.css   |  5 +++++
 2 files changed, 26 insertions(+)

diff --git a/docs/website/clients.php b/docs/website/clients.php
index c51138b2..7f214745 100644
--- a/docs/website/clients.php
+++ b/docs/website/clients.php
@@ -67,6 +67,27 @@ the user interface niggles when he gets around to it.</p>
 somewhat and that these instructions didn't exactly work... :-)  It turned out that these instructions worked <em>just fine</em> when I followed
 them to the letter the next day.  Go figure.  I think I need to record some screenshots of this one...</p>
 
+<h1>Cross-client Interoperability Considerations</h1>
+<p>If you intend to have users accessing the Really Simple CalDAV Store with more than one client
+then you should attempt to structure the URLs which they use to access the system in the way
+that Mulberry does it.</p>
+<p>Basically, Mulberry breaks the URL into three parts:</p>
+<ul>
+<li>The host name</li>
+<li>The root path</li>
+<li>Calendar namespace</li>
+</ul>
+<p>The host name is, of course, up to you.  The 'root path' should be <code>/caldav.php/</code> and anything following that is the calendar namespace.</p>
+<p>Within the calendar namespace RSCDS uses the first element of the path as the user or resource name, so that a client connecting at the root path
+can see all of the (accessible) users and resources available to them (Mulberry displays this hierarchy) with any calendars below that.</p>
+<p>Effectively this means that in Evolution, Sunbird and Lightning you should really specify a calendar URL which is something like:</p>
+<pre>
+caldav://calendar.example.net/caldav.php/username/home/
+</pre>
+<p>Then, when more calendar client software sees it as useful to be able to browse that hierarchy, you won't be up for any heavy database manipulation.</p>
+<p>I may well enforce this standard in some way before release 1.0, as well as auto-creating the <code>collection</code> records when Evolution, Lightning
+or Sunbird attempt to store to a non-existent collection.</p>
+
 <?php
  include("inc/page-footer.php");
 ?>
\ No newline at end of file
diff --git a/docs/website/style.css b/docs/website/style.css
index 7282d1d1..df365bf5 100644
--- a/docs/website/style.css
+++ b/docs/website/style.css
@@ -124,6 +124,11 @@ li {
   font-size: 90%;
   }
 
+code {
+  font-family: courier, courier new, fixed;
+  font-size: inherit;
+}
+
 pre {
   font-family: courier, courier new, fixed;
   font-size: 90%;