Salut,
gustav trede wrote:
>
>
> 2009/11/16 Igor Minar <iiminar_at_gmail.com <mailto:iiminar_at_gmail.com>>
>
> hi there,
>
> Is there some comprehensive documentation of a request life cycle?
>
> It often surprises me to find out that there is something going on
> with a request that I didn't know about, so a doc capturing all the
> processing phases and all classes that touch the request during it's
> life would be awesome.
>
> If not for grizzly v1, then v2 should definitely have that as a part
> of the documentation. A diagram would be the best.
>
> What do you think?
>
> /i
>
> There is a general need of documentation, design docs with flow diagrams
> and text explaining reasoning behind design decisions,
> theres several parts of the code that raises questions when you look at
> it , having to ask the author(s) every time is its self a waste of
> resources and only works as long as hes still available, has the time
> and remembers correctly.
> It could at least be present in the code unless theres some external
> tool available.
> Meeting notes, decisions taken when and why is another missing but
> important doc.
>
> The answer i gotten to the above is that this situation exists due to
> lack of resources.
>
> I was earlier forbidden from commenting inside the code, but i do it
> anyhow now. its essential to have it somewhere.
Agree. Actually that information Igor is asking for is existing inside
presentation, which sucks I know.
Like I said many times, v2 will not ship if we don't have a white paper
and back to back javadoc.
A+
-- Jeanfrancois
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> <mailto:dev-unsubscribe_at_grizzly.dev.java.net>
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
> <mailto:dev-help_at_grizzly.dev.java.net>
>
>
>
>
> --
> regards
> gustav trede
>
>