Received: by 10.58.187.138 with SMTP id fs10mr2143977vec.8.1350275618505;
        Sun, 14 Oct 2012 21:33:38 -0700 (PDT)
X-BeenThere: webpy@googlegroups.com
Received: by 10.52.89.80 with SMTP id bm16ls3090453vdb.9.gmail; Sun, 14 Oct
 2012 21:33:36 -0700 (PDT)
Received: by 10.52.91.168 with SMTP id cf8mr1478327vdb.6.1350275616463;
        Sun, 14 Oct 2012 21:33:36 -0700 (PDT)
Date: Sun, 14 Oct 2012 21:33:36 -0700 (PDT)
From: Dan Shechter <dans...@gmail.com>
To: webpy@googlegroups.com
Message-Id: <abf270b4-c749-4c67-aaa9-d1bb36b13a4e@googlegroups.com>
Subject: Using session with reloader - why not?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_1257_8617080.1350275616071"

------=_Part_1257_8617080.1350275616071
Content-Type: multipart/alternative; 
	boundary="----=_Part_1258_6346670.1350275616071"

------=_Part_1258_6346670.1350275616071
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi All,

Is there a reason not to always use the workaround for the session with 
reloader?

Thanks,
Dan.



------=_Part_1258_6346670.1350275616071
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi All,<div><br></div><div>Is there a reason not to always use the workaround for the session with reloader?</div><div><br></div><div>Thanks,</div><div>Dan.</div><div><br></div><div><br></div>
------=_Part_1258_6346670.1350275616071--

------=_Part_1257_8617080.1350275616071--