After the file has been served, do a forward to another page or servlet that makes the DB entry.
John
On Thu, 10 Jul 2003 14:54:49 -0500, Mark F <[EMAIL PROTECTED]> wrote:
I like that idea but it would require that I check every single request for
a matching pattern ( a download) and it seems to me that would produce a
significant amount of overhead, slowing the appserver quite a bit?
Thanks,
-Mark
Justin Ruthenbeck wrote:
|| Why not write a filter that puts an entry in a database table after
|| the file has been successfully served? This way you can log
|| whatever you want (who, what, when, size, ip address, duration,
|| application-specific info, etc). The report could then be run
|| whenever you need the information and from any machine with access
|| to the database (not necessarily a Java reporting solution).
||
|| This seems logical, especially since you, "will not only need to
|| record the download but query the database (or in this case
|| documentum) in order to check for a specific attribute relevant to
|| the report."
||
|| justin
||
||
|| At 11:38 AM 7/10/2003, you wrote:
||| Angus Mezick wrote:
|||| You mean, like use the items in the access log? You could always
|||| create a valve that watches for certain paths and updates a DB/file
|||| entry or some such.
|||| --Angus
||||
||||| -----Original Message-----
||||| From: Mark F [mailto:[EMAIL PROTECTED]
||||| Sent: Thursday, July 10, 2003 2:15 PM
||||| To: Tomcat Users List
||||| Subject: tracking downloads
|||||
|||||
||||| We need to track every time a file is downloaded from our
||||| server so that we may report on usage. We are currently
||||| migrating to a new Java/JSP (Documentum and WDK) based Web
||||| application. We wrote a perl script before under the old
||||| system to parse the log files and construct a report but I'm
||||| fairly certain there is a better way now that we are using
||||| Tomcat and Java. I thought about using a filter to increment
||||| a counter every time a request matched a particular pattern
||||| and I also thought about using the log file approach again
||||| this time using a java logging package but I'm not really
||||| sure what the best approach would be. Especially since we
||||| will not only need to record the download but query the
||||| database (or in this case documentum) in order to check for a
||||| specific attribute relevant to the report.
|||||
||||| Any ideas on how best to accomplish this are appreciated.
|||||
||||| -Mark
|||||
||||
|||| ---------------------------------------------------------------------
|||| To unsubscribe, e-mail: [EMAIL PROTECTED] |||| For additional commands, e-mail: |||| [EMAIL PROTECTED] ||| ||| ||| --------------------------------------------------------------------- ||| To unsubscribe, e-mail: [EMAIL PROTECTED] ||| For additional commands, e-mail: [EMAIL PROTECTED] || || || ____________________________________ || Justin Ruthenbeck || Software Engineer, NextEngine Inc. || justinr - AT - nextengine DOT com || Confidential || See http://www.nextengine.com/confidentiality.php || ____________________________________ || || || --------------------------------------------------------------------- || To unsubscribe, e-mail: [EMAIL PROTECTED] || For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
