Ticket #283 ( Closed )

Short Description Generate a NOOP HTML after RELEASE ?
Entered By: JaxAce When: 1999-04-26 16:35:12 Build: T1.03.29B
Categories Type: Question   Department: Product   Category: Not Categorized
For speed, we connect immediately in the home section. There is an unwanted side effect to this however: when a user needs to release a session, the call to 'exit' returns them to the home section. This is documented (see /surfer/exit ) but I missed it %-] The session is indeed released, but the user is connected again (to a new session) since we have the connect in the home section. Doh! I noticed that calls to release should be preceeded by a
but how pathto applies was note clear to me. Is there a simple way to wrapper the connect (or exit) with a
that would notice that the user has dropped? Or is there a better way to do this? - Using
 <TEEVENT Catch> 
seems risky. - Comparing the old session in a var to a new one seems like a waste of resources. - using Screen.SessionKey is errant, of course, since no session exits after release. Thanks for the great support! - Howard

Append By: Howard_Pautz@ml.com  When: 1999-04-26 16:37:56  New Status: Pending IE
<!-- sample code  -->


           <TEIF SomeSessionVar = 'NewSession'>

                <!-- hit and go --> 
                <TEACTION CONNECT "LU_GROUP_1">
                <TEPUTSECTION DEFAULT>

                Your Terminal is now Disconnected <br>




 <!-- we use the default section for 
      pass-thru emulation -->

 ... Happy Campers ...

 <A HREF="/surfer/exit/<TEMACRO SESSIONKEY>/
          <TEMACRO CLOCKTICKS>">Disconnect ?!</a><BR>

Append By: WindSurfer  When: 1999-04-27 00:37:18  New Status: Pending Customer
Comment I think that the best way to handle would be to reproduce what the "exit" URL does yourself, with a:
  when tranpath_1 is "cleanexit">
<title>Terminal Disconnected</title>
Your terminal is now disconnected...</b>


<!-- we use the default section for 
                    pass-thru emulation -->

... Happy Campers ...

<A HREF="/surfer/cleanexit/<TEMACRO SESSIONKEY>/
  <TEMACRO CLOCKTICKS>">Disconnect ?!</a><BR>
Append By: JaxAce  When: 1999-04-27 09:41:51  New Status: Pending IE
Comment Thought of that already, but tried the example you gave. Results: the session cannot disconnect because the session key is invalid - why, I don't know.
Could it be that having the exit URL in the default section, or that the default section is called in home via putsection, causes problems? 

Admin Console shows session at last screen, and still active. 

Exit URL contains proper key and ticks

Here's the resulting error message:

</td></tr></table></td></tr></table><H2>SurferScript Error Encountered</H2><p><table border><tr><td><b>Executing Section</b></td><td>global.cleanexit</td></tr>
<tr><td><b>Last recognized host connection screen</b></td><td>Not connected to a session or Unknown...</td></tr>
<tr><td><b>Failing Component</b></td><td>TEACTION GetSession</td></tr>
<tr><td><b>Description of Failure</b></td><td>Unable to connect to session-- UR
Append By: JaxAce  When: 1999-04-27 09:48:46  New Status: Pending IE
Comment Oops, sorry, that was HTML gobbletee gook; here's the human version of the error message:
SurferScript Error Encountered
Executing Section global.cleanexit 
Last recognized host connection screen Not connected to a session or Unknown... 
Failing Component TEACTION GetSession 
Description of Failure Unable to connect to session-- URL Contains no SessionKey name-value pair! 
Append By: JaxAce  When: 1999-04-27 09:51:37  New Status: Pending IE
Comment Ah Ha! Note the third line above - there never is a recognized screen because we hit default immediately after connecting! What to do? - Howard
Append By: WindSurfer  When: 1999-04-27 10:10:32  New Status: Pending Customer
Comment The real bug is in Windsurfer's first append-- the link inside default should be:
<A HREF="/surfer/cleanexit?SessionKey=<TEMACRO
 Disconnect ?!</a><BR>
The stock /surfer/exit command looks for the sessionkey in the URL, while transactions need it in a name-value pair...
Append By: JaxAce  When: 1999-04-27 10:17:22  New Status: Closed
Comment Super, the famous URLTWIRL parameter did the trick! thanks much - Howard