> I don't want to discount them at all! I'm just saying that I
> myself have
> no interest in this area (for now). With "big compromise" I
> mean stuff
> like giving up xml for config. I love XML. Hope that clarifies :D
I am not proposing giving up XML for config, I am proposing that
we make a way of generating hard-coded classes for constrained
devices where parsing is problematic and only serves to slow
down the deployment.
> Hey Berin, what are you using avalon for atm, and what will
> you likely
> be using it for in the future? Are you able to talk about that?
Now? I have the project for my book, but that is it. That is
squarely a Phoenix-based project.
Future? I am maintaining a project used at U.S. consolates that
has a GUI front end, and is currently very poorly designed.
I will be refactoring it (if possible) to use Avalon and
have a good design.
The project will incorporate Web Services (either interrop with
.Net server or a J2EE server), and a component based infrastructure
in the fat client. That will help with upgrading infrastructure
as needed.
Beyond that, I can share no details....
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
