DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=38311>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=38311 ------- Additional Comments From [EMAIL PROTECTED] 2006-02-03 23:03 ------- (In reply to comment #5) > Even leaving aside the confusion implied by the naming, the above > documentation would simply be incorrect. The "Registry" (or whatever the new > name is, for the sake of this note I'll continue to call it that) is an > internal structure to the SCXMLExecutor, and the developer/application does > not need to "provide a Registry" (just a limited number of its parts directly > via the SCXMLExecutor class API). > OK, then ignore the interpretation. Apologies for the misread. > But does ExecutionContext have potential for the same confusion w.r.t the > Context interface, as NotificationRegistry had with Registry? That was my > brief reference in comment #3. > > Suggestions for name: > > * ExecutionContext (pending question above) > * ExecutionEnvironment (suggestion from comment #2) > * ExecutionData > * ExecutionInstance > * --something else-- +1 for anything *Instance. ExecutionData seems overly vauge. Evnironment as well, but instance seems like a valid concept. So, in some Voice response system that might use SCXML to handle multiple conversations at once, one could say that there is one SCXML object that models states, etc. and multiple [ExecInstance|SCInstance|MachineInstance] whatever I'm also convinced that the value was this conversation, and that if you decided to call is "SuperMagicStateObject", we'd at least be able to refer someone to this Bugzilla thread to get context. So, consider views aired, but don't hold off on merging or committing. > > WDYT? > > -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
