[ZWeb] ratings redux

[Paul Everitt]

Shane and I discussed a few months ago a strategy that would make a hit 
counter not so problematic.  It basically involved putting the writes 
into a queue and having the data structure only written once every N 
minutes.  If you design it well for ZEO, avoiding hot spots, etc., then 
I think it can work.

If you could keep the writes down to under 50Kb of data a day or so, 
most people could live with that.

--Paul

Kapil Thangavelu wrote:
> --- Paul Everitt <paul@zope.com> wrote:
> 
> 
>>How related is this implementation strategy to one
>>for hit counters? 
>>The username as the key obviously would help much
>>less.
>>
> 
> 
> ugh.. i don't think i read this correctly the last
> time, a hit counter in the zodb, is still a bad idea.
> a download counter utilizing a btree length would be
> more effective. a hit counter would be bad, mainly
> because of size bloat in an undoable storage, and (i'm
> less sure on this one) from triggering a write
> transaction on page views which in zeo setting isn't a
> good idea. my current understanding is that in zeo1.0,
> only 1 transaction is allowed active at anyone time
> among all the zeo clients.
> 
> kapil
> 
> __________________________________________________
> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world's greatest free email!
> http://mail.yahoo.com/
> 
> _______________________________________________
> Zope-web maillist  -  Zope-web@zope.org
> http://lists.zope.org/mailman/listinfo/zope-web