on 1/12/01 1:54 PM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> The next step is to implement the second step of the process which is to
> create an additional portion that will allow us to have per-connection tools
> placed into the toolbox. These will be re-instantiated for each request
> (around the time the Page Module is executed) and then destroyed when the
> processing is over. I'm going to work on this part today and it should just
> be an extension of what we have in the PullService.
Ok, I'm having trouble figuring out how I should implement this. What I want
to have is the ability to have one or more objects that are instantiated and
stuffed into the Context at the Page level. However, I'm having difficulty
figuring out what to name them.
For example, for the Toolbox, we have $app as the default. Then, your tools
will be placed into $app.TOOL. For example, the UIManager is placed as
$app.ui.
I'm almost thinking that we should rename $app to $toolbox and then have
$app be application specific objects that are instantiated for each request.
I think that this would make more sense. Therefore, I could have $app.scarab
be an object that is instantiated for each request.
BTW, the reason why I need to have it instantiated for each request is that
this is an object that will be a container for several other objects and it
is a place much like RunData.set/getTemp(), however, it will generally
contain logic that is application specific.
Comments?
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
