Paul Hammant wrote:
Mauro,The main point to clarify is if Avalon aims to be *only* applicable to container/components architecture or aims (at least in some
On a related note, I have been thinking avout a fake commons logger (same package/class names,
different impl) that statically queues logged entries then fires them to the IoC enabled logger
when it is enabled. I could not it at Apache of course, but could at sourceforge.
As ever it is difficult even to advanced coders why Avaloners are idealigically opposed to static
logging in a multi-classloader container/component world..
- Paul
of its module - eg logging ) to be used in a wider OOP world.
Let me make an analogy with OS: it is widely accepted that Unix/Linux is has a more sophistiacated kernel than Windows/Mac
and is much more powerful - coming from a distributed design while Windows/Mac come from a desktop design.
Yet, most people (especially the ones with less technical requirements) find themselves drawn to Windows/Mac rather than Unix.
In my opinion, it is because W/M have managed to make things *easier* and *most* people don't need all the power of unix
for their desktops. So - one could go on and on with religious wars between OS - or try the marry the best aspects of both worlds.
A prime example is Mac OS X (of which I have very little experience - so I talk of heresay). But the principle remains that
it uses a core unix kernel with a highly user-friendly UI. It is up to the Mac user to decide how much of the unix power he/she wants
to use.
I guess my suggestion was to try to make Avalon the Mac OS X equivalent of server-sider programming - give as much as possible
the user the flexibility to choose if they want to do OOP or COP, or at least prepare a bridge for OOP to move to COP.
Cheers, Mauro
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
