<br><font size=2 face="sans-serif">> Chisel wrote:<br>
</font><font size=2><tt>> On Tue, Jan 02, 2007 at 07:42:41PM +0200,
Octavian Rasnita wrote:<br>
> > It gave errors when using $c->user in a controller or a template.
When not <br>
> > using $c->user, the program worked well.<br>
<br>
> We're making progress. Now about these errors - what do they actually<br>
> say?<br>
</tt></font>
<br><font size=2><tt>The errors were all about not being able to serialize
code refs.</tt></font>
<br><font size=2><tt>This was a pretty deep problem. It wasn't the
user object, but it was the session </tt></font>
<br><font size=2><tt>stuff, and not so much the session, but a need to
upgrade Tie::Refhash to fix the</tt></font>
<br><font size=2><tt>code ref thing.</tt></font>
<br>
<br><font size=2><tt>But, as he's said, and I can verify, Tie::Refhash
makes ActiveState Perl die during</tt></font>
<br><font size=2><tt>the tests.</tt></font>
<br>
<br><font size=2><tt>Further, I was not equipped with the knowledge to
debug these AS Perl deaths on my</tt></font>
<br><font size=2><tt>windows platform, else I would have tried.</tt></font>
<br>
<br><font size=2><tt>If there are some clues, pointers, etc. I'll give
it a try.</tt></font>
<br>
<br><font size=2><tt>My end result, was not using sessions, and therefore
incurring an additional DB query to</tt></font>
<br><font size=2><tt>get the user record on each request, but my site is
VLT (very low traffic) so the overhead</tt></font>
<br><font size=2><tt>is not a factor, and I don't have need presently for
anything else in session. </tt></font>
<br>
<br><font size=2><tt>Len.</tt></font>
<P><hr size=1></P><br>
<P><br>
This transmission may contain information that is privileged,<br>
confidential, legally privileged, and/or exempt from disclosure<br>
under applicable law. If you are not the intended recipient, you<br>
are hereby notified that any disclosure, copying, distribution, or<br>
use of the information contained herein (including any reliance<br>
thereon) is STRICTLY PROHIBITED. Although this transmission and<br>
any attachments are believed to be free of any virus or other<br>
defect that might affect any computer system into which it is<br>
received and opened, it is the responsibility of the recipient to<br>
ensure that it is virus free and no responsibility is accepted by<br>
JPMorgan Chase & Co., its subsidiaries and affiliates, as<br>
applicable, for any loss or damage arising in any way from its use.<br>
If you received this transmission in error, please immediately<br>
contact the sender and destroy the material in its entirety,<br>
whether in electronic or hard copy format. Thank you.<br>
</P>