Re: getSession, componentized but not async?

--===============4030258064450551671==
Content-Type: multipart/alternative; boundary=001a113f033a58529905370cd044

--001a113f033a58529905370cd044
Content-Type: text/plain; charset=UTF-8

>
> This can actually be useful in larger systems where you are making use of
> heavily componentized code, but in some cases it does seem like overkill.

That's close to the heart of the question. In larger systems, what is
useful about the componentized session objects in particular (as opposed to
components/adapters/interfaces in general)? It's a very particular API, so
I guess there's a reason for that.


> As for persisting session data-- I guess the idea is that storing or
> retrieving the session object doesn't need to be async because it is just
> an object in memory corresponding to a cookie in the request.


But doesn't that mean it's impossible to restart the process without
destroying user session data? That doesn't seem ok. Isn't that a problem
for your cas proxy?

Thanks Carl

DJM

--001a113f033a58529905370cd044
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span style=3D"font-size:12.8px">This can=
 actually be useful in larger systems where you are making use of heavily c=
omponentized code, but in some cases it does seem like overkill.</span></bl=
ockquote><div><span style=3D"font-size:12.8px">That&#39;s close to the hear=
t of the question. In larger systems, what is useful about the componentize=
d session objects in particular (as opposed to components/adapters/interfac=
es in general)? It&#39;s a very particular API, so I guess there&#39;s a re=
ason for that.</span></div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-styl=
e:solid;border-left-color:rgb(204,204,204);padding-left:1ex">As for persist=
ing session data-- I guess the idea is that storing or retrieving the sessi=
on object doesn&#39;t need to be async because it is just an object in memo=
ry corresponding to a cookie in the request.</blockquote><div><br></div><di=
v>But doesn&#39;t that mean it&#39;s impossible to restart the process with=
out destroying user session data? That doesn&#39;t seem ok. Isn&#39;t that =
a problem for your cas proxy?</div><div><br></div><div>Thanks Carl</div><di=
v><br></div><div>DJM</div><div><br></div><div><br></div></div>

--001a113f033a58529905370cd044--


--===============4030258064450551671==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Twisted-web mailing list
[email protected]
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-web

--===============4030258064450551671==--