[pve-devel] r4974 - pve-common/trunk

svn-commits at proxmox.com svn-commits at proxmox.com
Thu Aug 12 13:11:40 CEST 2010


Author: dietmar
Date: 2010-08-12 11:11:40 +0000 (Thu, 12 Aug 2010)
New Revision: 4974

Modified:
   pve-common/trunk/ChangeLog
   pve-common/trunk/README.dev
Log:


Modified: pve-common/trunk/ChangeLog
===================================================================
--- pve-common/trunk/ChangeLog	2010-08-12 11:08:48 UTC (rev 4973)
+++ pve-common/trunk/ChangeLog	2010-08-12 11:11:40 UTC (rev 4974)
@@ -1,3 +1,7 @@
+2010-08-12  Proxmox Support Team  <support at proxmox.com>
+
+	* RESTHandler.pm (AUTOLOAD): cache autoload
+
 2010-08-11  Proxmox Support Team  <support at proxmox.com>
 
 	* RESTHandler.pm (cli_handler): helper function to call method

Modified: pve-common/trunk/README.dev
===================================================================
--- pve-common/trunk/README.dev	2010-08-12 11:08:48 UTC (rev 4973)
+++ pve-common/trunk/README.dev	2010-08-12 11:11:40 UTC (rev 4974)
@@ -13,7 +13,7 @@
 the ExtJS Rich Internet Application Framework
 (http://www.sencha.com). 
 
-That framework, like any other ajax toolkit, can talk directly to the
+That framework, like any other AJAX toolkit, can talk directly to the
 REST API using JSON. So we were able to remove the server side
 template toolkit, which really reduces software complexity.
 
@@ -23,7 +23,8 @@
 We use JSON as data format, because it is simple and parseable by any
 web browser.
 
-Additionaly, we use JSON Schema [2] to formally describe our API.
+Additionaly, we use JSON Schema [2] to formally describe our API. So
+we can automatically generate the whole API Documentation.
 
 An great side effect was that we are able to use JSON Schema to
 produce command line argument parser automatically. In fact, the REST



More information about the pve-devel mailing list