Go for it! My weakness is naming things, and this is hidden under the covers enough that changes are not a problem.
On Wed, 23 Feb 2005 16:57:52 -0500, James Carman <[EMAIL PROTECTED]> wrote: > > > > All, > > > > While writing my article, I was having a difficult time describing "service > models" in HiveMind. To me, they're more logically described as "service > lifecycle models" or more succinctly "lifecycle models." Should we change > the documentation/code to reflect such a distinction? For these core > concept changes, it'd be better to make the changes earlier rather than > later. I think it would make the framework easier to understand. Any > thoughts? > > > > James -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
