Re: MRT's & SRT's

["Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>]

Yes, from a main storage POV, but you are both talking about the OS 
managing the program object, not the requester / user data.

When you write a web program,  do you set up persistent data structures 
to contain information about each requester?  And when a new request is 
received, does the program look up that requester's ID in those data 
structures?  The few that I've written simply use the info received from 
the browser to handle the request.

DeLong, Eric wrote:
> I think I agree with David on this one....  On iSeries, SLS ensures that a program object is only loaded into main storage once.  Each job that invokes that program manages the memory used by that program object for that instance.  This seems more akin to MRT, at least from main storage POV.
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Peter Dow (ML)
> Sent: Thursday, November 01, 2007 3:50 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: MRT's & SRT's
>
>
> I don't think so -- the instance specific data is usually on the 
> requesters machine, e.g. hidden input fields on a web page, or cookies.  
> Afaik, once a web page has been delivered to a browser, the system 
> forgets about it.
>
> David Gibbs wrote:
>   
> > Peter Dow (ML) wrote:
> >   
> >     
> > > Yes, in this day and age we are no longer concerned with whether the 
> > > program is in memory or not -- the OS handles that.  But the main 
> > > difference between SRT and MRT is whether the program has to maintain 
> > > information about the requester's process -- an SRT program does not, an 
> > > MRT program does.
> > >     
> > >       
> > In the System i world ... aren't all programs MRT's except the system
> > handles the instance specific data?
> >
> > david
> >
> >   
> >