> From: Leo Sutic [mailto:[EMAIL PROTECTED]
> 
> Simply put, there's no business case to be made for the migration
> effort. 

good point!

> 
> An aside: Part of the reason I'm into this aspect-container
> (whatever I'll end up calling it), is to provide this type
> of scalability. You should be able to build an Avalon app
> server, but also build something much smaller.

Again a very good point!

So my conclusion: 

1. Let's define component contracts as "rock-solid" and stable as
possible, having a bunch of testcases to ensure every aspect of those
contracts. This is what our "customers" are requesting and what makes
Avalon attractive to them and us. As less as possible migration needs in
the long future!
 
2. Let's try to modularize the core as much as possible, so that it can
be configured to different needs. This will broaden the user basis for
Avalon and makes it "the container of choice" 

Andreas 


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

Reply via email to