beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Updated: (BEEHIVE-789) PageFlowEventReporter.flowControllerDestroyed() does not expose the SessionID
Date Mon, 20 Jun 2005 19:31:27 GMT
     [ http://issues.apache.org/jira/browse/BEEHIVE-789?page=all ]

Rich Feit updated BEEHIVE-789:
------------------------------

    Fix Version: V1
                     (was: TBD)

> 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: v1m1
>  Environment: Windows XP
>     Reporter: David Read
>     Assignee: David Read
>     Priority: Minor
>      Fix For: V1

>
> 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


Mime
View raw message