You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2005/06/14 06:48:56 UTC

[jira] Assigned: (BEEHIVE-789) PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID

     [ http://issues.apache.org/jira/browse/BEEHIVE-789?page=all ]

Rich Feit reassigned BEEHIVE-789:
---------------------------------

    Assign To: David Read  (was: Rich Feit)

Hey David, would you close this if it's working for you?
Thanks,
Rich

> PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID
> -----------------------------------------------------------------------------
>
>          Key: BEEHIVE-789
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-789
>      Project: Beehive
>         Type: Improvement
>   Components: Samples
>     Versions: V1
>  Environment: Windows XP
>     Reporter: David Read
>     Assignee: David Read
>     Priority: Minor
>      Fix For: TBD

>
> If you want to track the lifetime of PageFlows, you might need to "see" the HTTP Session ID when the flow is destroyed.  Currently, the API only includes the flowController, and there's no public API to get the Session ID from the flowController.
> void flowControllerDestroyed( FlowController flowController );
> Note that having the request object (as a way to get the Session ID) probabaly wouldn't help here since the flow can be destroyed outside the context of a request (e.g. HTTP Session timeout).  It's probably more useful to have the ID exposed as part of the API.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira