From: Keats <ke...@su...> - 2003-07-27 02:29:01
|
I think you are zeroing in on a critical distinction here. The context tool "load on fault" mechanism allows you to avoid the overhead of creating new instances of context-aware objects. Putting context aware factories into each request would accomplish the same thing, but with higher overhead. (Actually this is virtually equivalent to the way it worked prior to Brian's latest changes, since the factories, CTs, were kept in a map within each context.) It's really a "pull" verses "push" provisioning model. Keats Lane Sharman wrote: > > > Marc Palmer wrote: > >> On Sat, 26 Jul 2003 13:46:36 -0700, Lane Sharman <la...@op...> >> wrote: >> >> >> Context doesn't need to know about ContextTools however. > > > This above statement is so confusing as to border on the curious. > Context.get(Object, Object) directly checks for a tool not in the > context and, if one is specified by the key, the tool value is placed in > the context. That is the way it works and this cannot be changed unless > you want to break backward compatibility. Could some other use for > context loading on a "fault" be dreamed up. Cannot think of one off hand. > > -Lane > > |