%Session Preserve property
9 views
Skip to first unread message
John A. Bertoglio
Sep 29, 2001, 1:56:52 AM9/29/01
to x...@info2.kinich.com
This is a multi-part message in MIME format.
------=_NextPart_000_004A_01C14870.DD4554D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I bought the Cache book (Object-Oriented Application Development...) =
from Germany and it had some documentation of the Preserve property of =
the %Session object I could not find in the ISC stuff. Apparently there =
is a property value of the property that allows weblink-style full =
symbol table writes. The docs in the book and the ISC documatic are not =
in agreement.
From the ISC docs:
property Preserve As %Integer [Initial =3D 0;]=20
A flag specifying the level of state preservation required by this =
session. You can change the value of this flag at any time.=20
This can take one of the following values:=20
a.. 0 The only state information that is preserved is the =
information in the %session object.=20
b.. 1 The entire state of the session process is preserved from one =
request to the next. This means that you tie up this Cache process for =
just this one user. As it uses the same process all local variables, =
locks, etc. are preserved from one request to the next
From the book:
The book has three states. 0, 1 and 2.=20
a.. 0 is the same in both=20
b.. In addition to the session object, all other open objects an =
local variables are saved and restored [between page hits]=20
c.. 2 is the same as 1 in the ISC docs
Which is correct?
------=_NextPart_000_004A_01C14870.DD4554D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>I bought the Cache book =
(Object-Oriented=20
Application Development...) from Germany and it had some documentation =
of the=20
Preserve property of the %Session object I could not find in the ISC =
stuff.=20
Apparently there is a property value of the property that allows =
weblink-style=20
full symbol table writes. The docs in the book and the ISC documatic are =
not in=20
agreement.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Trebuchet MS" size=3D2><STRONG>From the ISC=20
docs:</STRONG></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>property <B>Preserve</B> As =
<NOBR><A=20
href=3D"http://127.0.0.1:1972/apps/documatic/%CSP.Documatic.cls?APP=3D1&a=
mp;PAGE=3DCLASS&LIBRARY=3DUSER&CLASSNAME=3D%25Library.Integer">%I=
nteger</A></NOBR>=20
[Initial =3D 0;] </NOBR></DIV>
<BLOCKQUOTE>A flag specifying the level of state preservation required =
by this=20
session. You can change the value of this flag at any time.=20
<P>This can take one of the following values:=20
<UL>
<LI><B>0</B> The only state information that is preserved is the =
information=20
in the %session object.=20
<LI><B>1</B> The entire state of the session process is preserved =
from one=20
request to the next. This means that you tie up this Cache process =
for just=20
this one user. As it uses the same process all local variables, =
locks, etc.=20
are preserved from one request to the next</LI></UL></BLOCKQUOTE>
<DIV><FONT face=3D"Trebuchet MS" size=3D2><STRONG>From the=20
book:</STRONG></FONT></FONT></DIV>
<BLOCKQUOTE>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>The book has three states. =
0, 1 and=20
2. </FONT></DIV>
<UL>
<LI><FONT face=3D"Trebuchet MS" size=3D2>0 is the same in =
both</FONT>=20
<LI><FONT face=3D"Trebuchet MS" size=3D2>In addition to the session =
object, all=20
other open objects an local variables are saved and restored =
[between page=20
hits]</FONT>=20
<LI><FONT face=3D"Trebuchet MS" size=3D2>2 is the same as 1 in the =
ISC=20
docs</FONT></LI></UL>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>Which is=20
correct?</FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_004A_01C14870.DD4554D0--
------=_NextPart_000_004A_01C14870.DD4554D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I bought the Cache book (Object-Oriented Application Development...) =
from Germany and it had some documentation of the Preserve property of =
the %Session object I could not find in the ISC stuff. Apparently there =
is a property value of the property that allows weblink-style full =
symbol table writes. The docs in the book and the ISC documatic are not =
in agreement.
From the ISC docs:
property Preserve As %Integer [Initial =3D 0;]=20
A flag specifying the level of state preservation required by this =
session. You can change the value of this flag at any time.=20
This can take one of the following values:=20
a.. 0 The only state information that is preserved is the =
information in the %session object.=20
b.. 1 The entire state of the session process is preserved from one =
request to the next. This means that you tie up this Cache process for =
just this one user. As it uses the same process all local variables, =
locks, etc. are preserved from one request to the next
From the book:
The book has three states. 0, 1 and 2.=20
a.. 0 is the same in both=20
b.. In addition to the session object, all other open objects an =
local variables are saved and restored [between page hits]=20
c.. 2 is the same as 1 in the ISC docs
Which is correct?
------=_NextPart_000_004A_01C14870.DD4554D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>I bought the Cache book =
(Object-Oriented=20
Application Development...) from Germany and it had some documentation =
of the=20
Preserve property of the %Session object I could not find in the ISC =
stuff.=20
Apparently there is a property value of the property that allows =
weblink-style=20
full symbol table writes. The docs in the book and the ISC documatic are =
not in=20
agreement.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Trebuchet MS" size=3D2><STRONG>From the ISC=20
docs:</STRONG></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>property <B>Preserve</B> As =
<NOBR><A=20
href=3D"http://127.0.0.1:1972/apps/documatic/%CSP.Documatic.cls?APP=3D1&a=
mp;PAGE=3DCLASS&LIBRARY=3DUSER&CLASSNAME=3D%25Library.Integer">%I=
nteger</A></NOBR>=20
[Initial =3D 0;] </NOBR></DIV>
<BLOCKQUOTE>A flag specifying the level of state preservation required =
by this=20
session. You can change the value of this flag at any time.=20
<P>This can take one of the following values:=20
<UL>
<LI><B>0</B> The only state information that is preserved is the =
information=20
in the %session object.=20
<LI><B>1</B> The entire state of the session process is preserved =
from one=20
request to the next. This means that you tie up this Cache process =
for just=20
this one user. As it uses the same process all local variables, =
locks, etc.=20
are preserved from one request to the next</LI></UL></BLOCKQUOTE>
<DIV><FONT face=3D"Trebuchet MS" size=3D2><STRONG>From the=20
book:</STRONG></FONT></FONT></DIV>
<BLOCKQUOTE>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>The book has three states. =
0, 1 and=20
2. </FONT></DIV>
<UL>
<LI><FONT face=3D"Trebuchet MS" size=3D2>0 is the same in =
both</FONT>=20
<LI><FONT face=3D"Trebuchet MS" size=3D2>In addition to the session =
object, all=20
other open objects an local variables are saved and restored =
[between page=20
hits]</FONT>=20
<LI><FONT face=3D"Trebuchet MS" size=3D2>2 is the same as 1 in the =
ISC=20
docs</FONT></LI></UL>
<DIV><FONT face=3D"Trebuchet MS" size=3D2>Which is=20
correct?</FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_004A_01C14870.DD4554D0--
Chris Munt
Sep 29, 2001, 3:16:38 AM9/29/01
to x...@info2.kinich.com
John,
The ISC documentation is correct in this case. The book describes an
early version of CSP where the 'state-aware' mode was preserve mode '2'.
This was changed to '1' in later versions.
For all practical purposes you can regard preserve mode = '1' as being
equivalent to WebLink's state-aware mode.
Also, CSP's hyperevents are conceptually equivalent to WebLink's Event
Broker calls.
Regards,
Chris.
In article <3bb56...@info2.kinich.com>, John A. Bertoglio <jb@co-
laboratory.com> writes
> Preserve property of the %Session object I could not find in the
> ISC stuff. Apparently there is a property value of the property
> that allows weblink-style full symbol table writes. The docs in the
> book and the ISC documatic are not in agreement.
>
> From the ISC docs:
>
> property Preserve As %Integer [Initial = 0;]
>> information in the %session object.
>> *> 1 The entire state of the session process is preserved from
>> one request to the next. This means that you tie up this Cache
>> process for just this one user. As it uses the same process
>> all local variables, locks, etc. are preserved from one reques
>> *> In addition to the session object, all other open objects an
>> Which is correct?
---------------------
Chris Munt
ITA Consulting Ltd
Royal Marsden NHS Trust
M/Gateway Developments Ltd : http://www.mgateway.com
---------------------
The ISC documentation is correct in this case. The book describes an
early version of CSP where the 'state-aware' mode was preserve mode '2'.
This was changed to '1' in later versions.
For all practical purposes you can regard preserve mode = '1' as being
equivalent to WebLink's state-aware mode.
Also, CSP's hyperevents are conceptually equivalent to WebLink's Event
Broker calls.
Regards,
Chris.
In article <3bb56...@info2.kinich.com>, John A. Bertoglio <jb@co-
laboratory.com> writes
> I bought the Cache book (Object-Oriented Application
> Development...) from Germany and it had some documentation of the
> Preserve property of the %Session object I could not find in the
> ISC stuff. Apparently there is a property value of the property
> that allows weblink-style full symbol table writes. The docs in the
> book and the ISC documatic are not in agreement.
>
> From the ISC docs:
>
> property Preserve As %Integer [Initial = 0;]
>> A flag specifying the level of state preservation required by
>> this session. You can change the value of this flag at any time.
>
>> This can take one of the following values:
>
>> *> 0 The only state information that is preserved is the
>> This can take one of the following values:
>
>> information in the %session object.
>> *> 1 The entire state of the session process is preserved from
>> one request to the next. This means that you tie up this Cache
>> process for just this one user. As it uses the same process
>> all local variables, locks, etc. are preserved from one reques
>> t to the next
> From the book:
>> The book has three states. 0, 1 and 2.
>> *> 0 is the same in both
> From the book:
>> The book has three states. 0, 1 and 2.
>> *> In addition to the session object, all other open objects an
>> local variables are saved and restored [between page hits]
>> *> 2 is the same as 1 in the ISC docs
>> Which is correct?
---------------------
Chris Munt
ITA Consulting Ltd
Royal Marsden NHS Trust
M/Gateway Developments Ltd : http://www.mgateway.com
---------------------
John A. Bertoglio
Sep 30, 2001, 9:18:01 PM9/30/01
to x...@info2.kinich.com
Chris:
Thank you for the response.
If I follow the documentation, the missing mode models the WLD behavior of
saving the entire symbol table automatically. Therefore, (if I am paying
attention) in stateless mode you must manually insert data into the %session
object in order preserve it between page loads.
While I understand the overhead involved with automatically preserving
vars/objects, it would have been a nice option.
jb
"Chris Munt" <c...@cmunt.demon.co.uk> wrote in message
news:YSWYGUAWVXt7Ewu$@cmunt.demon.co.uk...
Thank you for the response.
If I follow the documentation, the missing mode models the WLD behavior of
saving the entire symbol table automatically. Therefore, (if I am paying
attention) in stateless mode you must manually insert data into the %session
object in order preserve it between page loads.
While I understand the overhead involved with automatically preserving
vars/objects, it would have been a nice option.
jb
"Chris Munt" <c...@cmunt.demon.co.uk> wrote in message
news:YSWYGUAWVXt7Ewu$@cmunt.demon.co.uk...
Reply all
Reply to author
Forward
0 new messages