<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>Re: [Seaside] Seaside Access/Activity Logging</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>The biggest benefit to outside reporting tools is not having to reinvent the wheel...<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Tue Aug 24 08:37:02 2010<BR>
Subject: RE: [Seaside] Seaside Access/Activity Logging<BR>
<BR>
On Tue, 24 Aug 2010 04:58:44 -0700, "Boris Popov, DeepCove Labs \(SNN\)"<BR>
<boris@deepcovelabs.com> wrote:<BR>
> Having said that, I just noticed GA has a limit of approximately 500<BR>
> requests per session, so this may not work as well as one could hope...<BR>
<BR>
Just a stupid question.. Why not just use some sort of audit<BR>
log that is built into the code that tracks users movement from<BR>
page to page? I realize that you'll need to contiously put the<BR>
auditlog calls in place but it seems like that ought to do the<BR>
trick and you could effectively log whatever you wanted (session<BR>
details, logged in user info, etc)..<BR>
<BR>
I realize that some of these other methods are just fine but...<BR>
I guess there's more than one way to fillet a trout (ok -- maybe<BR>
not for a trout).. :-)<BR>
<BR>
-- Rick<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>