That was a good start to which there was one reply that was a question
by you asking if the change to the jbossmq layer would work. There were
other messages threads in which elements of this was discussed, but I
never got the feeling from these that a decision had been made as to the
efficacy of the approach. There was no concluding "this is how we have
worked it out..." concluding message that I saw. Maybe I missed.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 11:47 AM
Subject: Re: [JBoss-dev] communicating changes


> Like this?
>
http://www.mail-archive.com/jboss-development%40lists.sourceforge.net/msg110
85.html
>
> david jencks
>
> On 2001.11.13 13:43:12 -0500 Scott M Stark wrote:
> > Part of the problem with communicating architecture changes is that
> > discussions are embedded in threads whose subject ultimiately is
> > virtually meaningless for the concluding remarks. Also, the conclusions
> > about what is to be done are often left implied based on the thread
> > arguments.
> >
> > If your going to make an architectural change, especially if it is an
> > incomptible
> > one, clearly state that is a message with an approriate subject that
> > concludes
> > with a task list of the changes.
> >
> > xxxxxxxxxxxxxxxxxxxxxxxx
> > Scott Stark
> > Chief Technology Officer
> > JBoss Group, LLC
> > xxxxxxxxxxxxxxxxxxxxxxxx
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
>


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to