On Thu, Jul 19, 2001 at 02:55:33PM -0700, Todd Caine wrote:
> I guess I wasn't very clear. The component is being kept alive by the use of
> an alias. The session which posted to the component keeps stopping before the
> component can post back to it. So my problem isn't that the component is dying
> prematurely but the session who is requesting something from the component. I
> don't have any reason to store a postback immediately because their are a
> couple of different postback()'s that can be created and called depending on
> what happens in the component itself. The only reasonable way to keep the main
> session, not the component, alive is to increment the sender's ref count in the
> component. How are session which are using components expected to stay alive?
Then use a postback that you don't call. Anyway, if it requests something
then the components probably needs to return something. You need some sort
of postback for it. If it doesn't returns anything then you could post all
events to the component at once. The session would have to create the
postback, don't let the component create it from $_[SENDER]. Components
should know anything about the sessions that call them.
Sorry if I don't see the point.
Torvald
