In keeping with my last post...

There have been some great discussions on this list, and presumably on 
other lists such as those devoted to Avalon, that imply some deep 
underlying models of what makes good web architecture and good software 
design.  In some cases these discussions have led to some valuable results,
  such as the Avalon and Excalibur frameworks.  However my opinion, as 
someone who lurks on the Cocoon lists, is that much of the discussions 
disappear into the ether.  The "Developer's Guide version 1.0 for Avalon 
Framework" is a really great example of how some of these discussions can 
become useful resources for newbies or those, such as myself, who are less 
inclined to ponder deep issues.

I realize that the "deep thinkers" in the Cocoon sphere are busy pushing 
the envelope, making fixes, and generally making Cocoon a great project.  
However there are some discussions that I feel need to be recorded, 
otherwise they will continue to be points of contention and concern.  
Stefano, though his RTs and the discussion they engender, is the primary 
"culprit", but there are others on the list who could also contribute their 
conceptual models and approaches.

The kinds of things I am referring to include (off the top of my head):

   - SoC (What does a concern look like? How much separation is enough? Etc.
)
   - The "proper" design of URLs (.../cocoon1 vs. .../cocoon/old vs. ...)

<grumble>
People on this list do step in and say "this is mixing concerns" and "that'
s not a proper URL".  This is a good thing for Cocoon.  However, to 
paraphrase, "Tell a developer not to do something and you fix the current 
implementation/design.  Teach them how to recognize good and bad things, 
and you fix all future implementations/designs."  I want to learn, damnit!
</grumble>

The subject of the message was intended to elicit from Stefano his 
heuristics regarding designing URLs.  Even a bunch of references would be 
nice, although in my opinion Tim Berner-Lee's discussions, which I imagine 
would be a reference, aren't that understandable.  However I would ask that 
any of you who have similar design heuristics share them with us.  Please!

Jason Foster


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

Reply via email to