Simon Redding ([EMAIL PROTECTED]; Thursday, July 11, 2002 9:34 AM):
> Having been around the 'web works' documents on a number of > occasions, I'm well aware of how the Internet works, so please don't > flame me. > On the other hand, I'm trying to establish concurrency for a > pre-packaged J2EE web app (to record timesheets) which has Apache as > a presentation tier. All the users are on a flat corporate > Intranet, which has no proxies, IP address masking etc etc that > would skew session/visit information. Normal time to complete the > application (i.e. fill in a timesheet) would be about 10 minutes, > with quite a lot of page requests in that time (it's not a great > app). All I want to know is the number of 'concurrent users', which > I would take to mean the number of sessions that have not timed out > on the keep-alive (or at the application level are from an IP > address which has sent a request in the last (say) 10 minutes). Well, you are still dealing with browser caches. And there is no way to know when a user leaves the last page. All this is covered in web works, so I'm sure you know it. > Can analog do this? Can anyone recommend a better package/solution? > Can anyone save my sanity? ;"( Analog won't do this. You could gather stats at the application level, since the J2EE interface provides session management. I don't know of any non-commerical packages that give estimates of session length. I can name some commercial ones, but that might be heresy on this list. :-) -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
