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

Reply via email to