From 55fe371db99eb18369bfc743af192f105cb92418 Mon Sep 17 00:00:00 2001
From: Jesse Young <youngj@envaya.org>
Date: Fri, 23 Sep 2011 23:19:41 -0700
Subject: [PATCH] explain multipart sms in api reference

---
 .phrozn/entries/serverapi/index.twig | 4 +++-
 history/index.html                   | 4 ++--
 serverapi/index.html                 | 4 +++-
 3 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/.phrozn/entries/serverapi/index.twig b/.phrozn/entries/serverapi/index.twig
index c4d25e0..1ad8c42 100755
--- a/.phrozn/entries/serverapi/index.twig
+++ b/.phrozn/entries/serverapi/index.twig
@@ -257,6 +257,7 @@ Additional parameters sent in POST requests with action=incoming:
     <dt>"message" ::= &lt;text&gt;</dt>
     <dd>
         The message body of the SMS, or the content of the <code>text/plain</code> part of the MMS.
+        For multipart SMS messages, this field contains all parts concatenated and may be longer than 160 characters.
     </dd>
 </dl>
         
@@ -396,7 +397,8 @@ The Content-Type header should be text/xml, with the content as follows:
         <dl>
         <dt>CDATA</dt>
         <dd>
-            The content of the SMS message to send.
+            The content of the SMS message to send. If the content is longer than the maximum size of a single SMS (typically 160 characters),
+            it will automatically be sent as a multipart SMS.
         </dd>
         </dl>
     </dd>
diff --git a/history/index.html b/history/index.html
index c0e5ae8..207ccc9 100755
--- a/history/index.html
+++ b/history/index.html
@@ -39,7 +39,7 @@
     
     <h2>History</h2>
   
-    Version 2.0-beta (2011/09/22)
+    Version 2.0-beta (2011/09/23)
 
 <ul>
     <li>
@@ -51,7 +51,7 @@
     <li>
         Send and receive multipart SMS (longer than 160 characters)
     </li>    
-    <li>   
+    <li>
         Server API changed to use POST requests instead of GET requests, and other changes; 
         support for future server API changes via 'version' request parameter
     </li>        
diff --git a/serverapi/index.html b/serverapi/index.html
index ac4fc83..db9a89a 100755
--- a/serverapi/index.html
+++ b/serverapi/index.html
@@ -295,6 +295,7 @@ Additional parameters sent in POST requests with action=incoming:
     <dt>"message" ::= &lt;text&gt;</dt>
     <dd>
         The message body of the SMS, or the content of the <code>text/plain</code> part of the MMS.
+        For multipart SMS messages, this field contains all parts concatenated and may be longer than 160 characters.
     </dd>
 </dl>
         
@@ -434,7 +435,8 @@ The Content-Type header should be text/xml, with the content as follows:
         <dl>
         <dt>CDATA</dt>
         <dd>
-            The content of the SMS message to send.
+            The content of the SMS message to send. If the content is longer than the maximum size of a single SMS (typically 160 characters),
+            it will automatically be sent as a multipart SMS.
         </dd>
         </dl>
     </dd>