hammant 01/12/03 01:03:08
Modified: src/xdocs book.xml phoenix.uris
Added: src/xdocs afuture.xml
Log:
new page for future of Phoenix
Revision Changes Path
1.10 +1 -0 jakarta-avalon-phoenix/src/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/book.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- book.xml 2001/11/16 10:42:59 1.9
+++ book.xml 2001/12/03 09:03:08 1.10
@@ -12,6 +12,7 @@
<menu-item type="external" id="downloads" label="Download"
href="http://jakarta.apache.org/builds/jakarta-avalon/release/phoenix"/>
<menu-item label="Getting Started" href="getting-started.html"/>
<menu-item label="Installation" href="install.html"/>
+ <menu-item label="A Future" href="afuture.html"/>
<menu-item label="Todo" href="todo.html"/>
<menu-item label="Changes" href="changes.html"/>
<menu-item type="external" id="api-docs" label="API Docs"
href="api/index.html"/>
1.7 +1 -0 jakarta-avalon-phoenix/src/xdocs/phoenix.uris
Index: phoenix.uris
===================================================================
RCS file: /home/cvs/jakarta-avalon-phoenix/src/xdocs/phoenix.uris,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- phoenix.uris 2001/11/16 10:42:50 1.6
+++ phoenix.uris 2001/12/03 09:03:08 1.7
@@ -18,6 +18,7 @@
blockinfo-specification.html
creating-a-block.html
example-configuration.html
+afuture.html
images/add.jpg
images/fix.jpg
images/remove.jpg
1.1 jakarta-avalon-phoenix/src/xdocs/afuture.xml
Index: afuture.xml
===================================================================
<?xml version="1.0"?>
<!DOCTYPE document SYSTEM "dtd/document-v10.dtd">
<document>
<header>
<title>A future</title>
<authors>
<person name="Paul Hammant" email="[EMAIL PROTECTED]"/>
</authors>
</header>
<body>
<s1 title="Overview">
<p>
A long term aim of Phoenix is to provide a platform that hosts
multiple third party applications written only in Java within a single virtual
machine. The Phoenix platform is currently hosted on an Operating System such
as Unix, Windows or Mac. It could function directly on top of a Java Operating
System. A CPU combined with a suitable amount of memory, a basic BIOS, a
Kernal, a suitable JVM and runtime library, could mount Phoenix and hosted
server applications.
</p>
</s1>
<s1 title="One step further">
<p>
Imagine Sun making such a box under their own name or as Cobalt,
using low power chips from their own stable or perhaps a StrongARM. That
machine could be rack mounted like their current X1:
</p>
<figure>
<title>Sun X1</title>
<graphic srccredit="© Sun Microsystems"
fileref="http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg";
format="JPEG"/>
</figure>
<p>
If that rackable server had 32 such CPUs, each with 128Mb of memory
all booting Phoenix. And if the CPUs shared a single hard drive, we might have
a machine that was tuned to CPU intensive activities. Cocoon/Tomcat, EJB
clusters, might be load balanced by one of the CPUs running a Phoenix load
balancer. Alternate scenarios are for virtual site hosting. It could be a
"1U" render or bean farm with each internal CPU having its own TCP/IP address.
</p>
</s1>
<s1 title="Is all this possible?">
<p>
Well there are already romable J2SE implementations that are
available for StrongARM chips on Compaq's handheld iPAQ. We are there already,
but for the client side rather than the server side.
</p>
</s1>
</body>
</document>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
![http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg"](http://www.sun.com/products-n-solutions/hw/networking/images/prodsplash/x1.jpg"){kind=link}