If you use the TEACTION RELEASE KEEPOPEN, the session is 
put back in a pool of available sessions.  However, the 
CONNECT documentation does not state that it will return 
one of these sessions if available.  Is that the flow in 
this case?  That a CONNECT will first look for sessions 
that have been released with keepopen, and if none are 
available, then go to the host for a new one?

thanks

Pete, I do not know if it is a "hard-wired" rule in 
Screensurfer for the "connect" action to connect back to 
previously released "keptopen" sessions first before 
establishing a new host connection but in all the testing 
I've done that seems the case.  This is why you check 
the "screen.screenid" variable to see which host screen you 
are on...

I'd like to know for absolute sure, please, as we are in 
the process of designing some high-volume, high-response 
projects, and session reuse is a key component of the 
design.

thank you

For sure, the available (started, but released-keepopen) 
sessions are the first to be acquired in a TEACTION CONNECT.

The logic scans the sessions first for AVAILABLE, then if 
none found, scans for STOPPED, then if none found scans for 
timed-out.

In a point release later this year, rather than scanning we 
will be implementing internal queues so that very large 
numbers of sessions on one machine don't impose any 
allocation CPU overhead...with identical logic, just better 
efficiency for finding the next available session.

OK, sounds good - thanks