On 01-05-2014, Bert JW Regeer wrote:
>
> --Apple-Mail=_8BFE3C8B-DFF0-491C-A72C-E7137EA10853
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain;
>       charset=iso-8859-1
>
>
> On May 1, 2014, at 12:39 , wilk <w...@flibuste.net> wrote:
>
>> On 30-04-2014, Bert JW Regeer wrote:
>>=20
>> About _session_id of pyramid_pluggable_session
>>=20
>>> That is why it has an underscore prepended, this makes it an internal=20=
>
>>> =3D
>>> value that can not be relied on, unless you always use my session =3D
>>> package. The nice thing is that with mine you can keep using it, as =
> long =3D
>>> as you swap out the plugs, and they won=3D92t ever alter the fact =
> that =3D
>>> there is a _session_id.
>>=20
>> Sorry it's not clear for me, when i write a new plug can i rely on=20
>> _session_id ?
>>=20
>> --=20
>> William
>>=20
>
> Yes. You can rely on _session_id existing. =46rom an outside =
> perspective, anyone using request.session SHOULD NOT rely on _session_id =
> existing, since it may not be pyramid_pluggable_session, and thus =
> _session_id may not be available.

I understand, thanks

-- 
William

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Reply via email to