Jason Foster wrote:
> 
> <snip/>
> 
> Gut, snap reactions:
> 
> - This feels like it relates to the work of the W3 TAG (Technical
> Architecture Group)

Nah, they deal with stuff like ultimate scalability of the *entire* web.
Much bigger perspective.

> - I don't know from where the Avalon developers obtained their visions,
> but they seem to have hit a sweet spot with respect to flexibility and
> rigour.  

Thanks, I consider this a compliment, being part of the team who started
the Avalon vision.

> I think it will be very difficult to find a similar sweet spot
> for Cocoon (which shouldn't stop the attempt!) given what I see as the
> primitive nature of most web development... Perl print statements are
> *still* the dominant form!

That is the same argument I heard when starting Avalon :)

> - Documentation and examples will be absolutely vital.  

Absolutely. Expect a few *important* thing on this side during the
course of this year.

> SoC, IoC, and
> contracts are still difficult for me to understand, and I've been trying
> for a while now.  Granted I'm not the most astute programmer, but I don't
> think I'm that bad.  These concepts seem more like practices, and as such
> exist more in documentation and examples than in interfaces and classes.
> - On a picky note, I would prefer a polymorphic syntax that doesn't mess
> with the specification for URLs ... we've become pretty good about leaving
> these alone so why stop now?  A subprotocol might be a good choice (eg.
> polymorphic:skin://docbook...)

Ok, good point, although I'm not sure if 

 polymorphic:skin://

is any more URI compliant than

 component[skin]://

> - Let's get cracking so that the content-management group can produce that
> tool I'm waiting for :)

:)

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<[EMAIL PROTECTED]>                             Friedrich Nietzsche
--------------------------------------------------------------------



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

Reply via email to