[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

205.0. "Threads/Tasks/Sessions" by AIMTEC::PORTER_T (Terry Porter, ALL-IN-1 Support, Atlanta CSC) Mon Mar 09 1992 23:09

In the FCS audit information it refers to Threads, Tasks and Sessions, what are
the correct definitions of these terms?

I thing I know what a Thread is, it is the context in which the FCS carries
out work. Which means that there will be one thread for each, task, session
or housekeeping activity. Right?

What is the difference between a Task and a Session? Is a session a connection
from a client or a FCS manager, and a task the work involved in satisfying
a single request from a client. If this is correct there would be many
tasks in the context of a fewer number of sessions. Is this correct?

Assuming the above are more-or-less correct ...

Is a different thread used for each task, or is the same thread used for all
the tasks in a session?

Lots of questions, thanks in advance for any answers,

Terry
T.RTitleUserPersonal
Name		DateLines
205.1CHRLIE::HUSTONTue Mar 10 1992 15:1254
    
    Geez Terry you are keeping me busy this morning :-)
    
>I thing I know what a Thread is, it is the context in which the FCS carries
>out work. Which means that there will be one thread for each, task, session
>or housekeeping activity. Right?

    A thread is basically an execution path for the server. Each incoming 
    request gets its own thread, there can be multiple threads per session
    (asynch calls the most common way of getting this) and there could
    be multipel threads per task.
    
    Also there are several background thread (housekeeping as you put it)
    like the garbage collction thread for instance
    
>What is the difference between a Task and a Session? 
    
    A session is basically a user connection while a task is a request on
    behalf of a session.
    
    >Is a session a connection
>from a client or a FCS manager, and a task the work involved in satisfying
>a single request from a client. 
    
    Basically yes. A session is created for every connection to the FCS 
    be it a client, manager or another server (brokered operation). Each
    session will have a task, possibly multiple tasks.
    Each task gets its own thread.
    
    >If this is correct there would be many
>tasks in the context of a fewer number of sessions. Is this correct?

    Yup, possibly. If all calls are synchronous calls then there would be 
    a single task active for a session. There could be no open task for a 
    session.  If you make asynch calls then you can have multiple active
    tasks per session. I believe ALL-IN-1 makes all asynch calls.
    
    
>Assuming the above are more-or-less correct ...

    close enough to move on :-)
    
>Is a different thread used for each task, or is the same thread used for all
>the tasks in a session?

    Each task gets a different thread. Wehn the server receives a request
    it creates a thread. When the task is done, all its threads are killed.
    
>Lots of questions, thanks in advance for any answers,
    
    Hope that answers them all.
    
    --Bob
205.2Thanks for the helpAIMTEC::PORTER_TTerry Porter, ALL-IN-1 Support, Atlanta CSCTue Mar 10 1992 15:4513
Bob,

Thanks for your help in answering my many questions. There will probably be
many more before I have finished, I havn't even started looking at 
troubleshooting in detail yet ;^}

Seriously, I appreciate all the help I am getting in putting together this 
course, hopefully the CSC will be better prepaired for the support of the FCS
and have to raise fewer problems to engineering.

Thanks, and keep up the good work :-)

Terry