From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason McCandless Subject: xen http interface - xensv Date: Wed, 8 Jun 2005 13:12:06 +0100 Message-ID: <828da56f050608051220435dc3@mail.gmail.com> Reply-To: Jason McCandless Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1104958071==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1104958071== Content-Type: multipart/alternative; boundary="----=_Part_678_29486975.1118232726991" ------=_Part_678_29486975.1118232726991 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, What is the status of xensv currently? Why has it been dropped from=20 unstable? I am considering picking up the torch. Would I be better advised to start= =20 anew with apache and perl/python/whatever instead of the twisted framework= =20 used in xensv. Jason ------=_Part_678_29486975.1118232726991 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,
What is the status of xensv currently? Why has it been dropped from unstabl= e?

I am considering picking up the torch. Would I be better advised to start anew with apache and perl/python/whatever instead of the twisted framework used in xensv.


  Jason
------=_Part_678_29486975.1118232726991-- --===============1104958071== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1104958071==--