Berin, Noel,

> > AvalonDB isn't a component, but a server or application--much the
> > same way JAMES is.  As such, it doesn't really fit the charter of
> > what we do.
> 
> I stand corrected.  I thought that AvalonDB was a reusable a JDBC database
> component that, for example, James could use.  As it is, I am looking to
> embed HypersonicSQL, using the Avalon supplied code, for that purpose.
> 
> I do wonder whether or not Paul & Co ought to see whether or not it might
> make sense to merge with axion.  Why do things redundantly if there is the
> possibility of collaborating?

* AvalonDB is a set of A-F enabled components.  It can be laced together in a mainable 
bootstrap,
from another set of components, or with the supplied assembly.xml, xinfos etc inside 
Phoenix as a
SAR app.  

It is not complete.  Jason Van Zyl chatted to me at the outset, but we chose not to 
join forces on
teh Axion project.  

The HSQL comp is the same as (*) above.

To be honest, in my perfect world Avalon.apache.org there is room for servers too.  If 
I were to
write from scratch a mail server, I'd put it there.  Clearly though when Phoenix as a
semi-independant project has it's mail list collapsed (not withstanding that Ulrich 
still posts to
it ;-) we defined that this was a far simpler shop.

- Paul


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to