From: Honza M. <hon...@ec...> - 2005-07-20 08:36:55
|
Hi Michael, > I just wonder how this works with cached data (views, site module). Doe= s the=20 > caching also store the hit data or do cache hits simply not count (as I= would=20 > have thought)? The hits to cached data displayed by slice.php3 or view.php3 are counted. It is done during parameter parsing, where cache is not involved, yet. It is different in sitemodule - site.php3. In this case it is hard to know, for which item id we should update the counter (the ids are somehow hidden in apc variable). So, the hit is count only if the content is not rendered from cache. The solution in this case could be to call=20 CountHit(<long_or_short_id>);=20 from site control file. In this case you should use all the views in the site with 'o' parameter (instead of 'x') in order the items not generated from cache aren't counted twice. If you have any idea, how to improve site module hit-counting, let share the idea with us, please. Hope it helps, Honza =20 V St, 20. 07. 2005 v 00:15, Michael Moritz p=ED=B9e: > On Tuesday 19 July 2005 22:52, Honza Malik wrote: > > Well, I have to correct this info a bit. You are right Norbert, all t= he > > "hits" are recorded to the "log" table, but it is there only for a ve= ry > > limited time (seconds/minutes). > > > I just wonder how this works with cached data (views, site module). Doe= s the=20 > caching also store the hit data or do cache hits simply not count (as I= would=20 > have thought)? >=20 > mimo >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl= ick > _______________________________________________ > Apc-aa-coders mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apc-aa-coders --=20 Honza Malik <hon...@ec...> Econnect |