MIME-Version: 1.0
In-Reply-To: <38C0BFD50092414E900DEE15F8976FE0@sb.litts.net>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Disposition: inline
References: <38C0BFD50092414E900DEE15F8976FE0@sb.litts.net>
Content-Type: text/html; charset="UTF-8"
Message-ID: <rt-3.8.6-60453-1284580962-207.22096-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
Content-Length: 968

Thank you for your feedback on the XML channel.<br />
<br />
From a design point of view, I intentionally did not split the data apart but instead returned the whole thing.&nbsp; This was intentional until we could make it into a more RESTful style.<br />
<br />
It is probably time to actually take on the work of splititng the data into chunks.&nbsp; A simple RESTful API for gathering information about a server, in my mind anyway, was along the lines of:<br />
<br />
/views -- returns a list of views<br />
/views/_default -- returns information about a specific view<br />
/views/_default/zones&nbsp; -- returns a list of zones in a particular view<br />
/views/_default//zones/isc.org -- returns detailed information about this particular zone<br />
<br />
and so on.&nbsp; I am not certain if the /config, /stats, or /status information should be before or after the URIs in this simple example.&nbsp; My gut tells me after.<br />
<br />
--Michael<br />
<br />